WhenIsBins

Where it sits in the directory's order

What can be seen from outside, weighed as the directory publishes.

Where it answers

• https://whenisbins.com/mcpstreamable-http

The tools it lists (4, as of 9 hours ago)

The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.

• find_addresses

  Step 1. Lists the properties the council knows at a UK postcode and names the input get_collections needs (required_input). Show the user the candidates and let them choose, unless what they told you matches exactly one candidate. Rules: never guess or choose a property for the user; if their address is not in the list, say so. Use only the dates returned: never extend a pattern, move a date for a bank holiday or work out a weekday yourself (read by_date). Say when a result is provisional or is not the user's exact property. Offer opt-in evening check-ins only if your host can schedule them. A

• get_collections

  Step 2. Looks up collection dates for the one property the user chose. Send the postcode and the field find_addresses named in required_input (normally property_id, from the chosen candidate). Waits up to about 45 seconds. status is done, partial (provisional dates), still_working (use check_lookup; never call this again for the same property) or failed. What goes in the containers is summarised in collections[].contents when present. If contents is null, say the council has not published contents in the evidence held; never guess from colour or name. accepted combines council labels across co

• check_lookup

  Reads a lookup that get_collections started, by its lookup_id. Waits up to about 30 seconds. Same statuses as get_collections. What goes in the containers is summarised in collections[].contents when present. If contents is null, say the council has not published contents in the evidence held; never guess from colour or name. accepted combines council labels across containers: use appearance_occurrences items for each container and condition, especially when varies_by_date is true. Rules: never guess or choose a property for the user; if their address is not in the list, say so. Use only the d

• get_schedule

  For a repeat check. Reads the stored schedule for a property_id that an earlier done lookup returned. It starts no new lookup; if it reports no_schedule, run find_addresses and get_collections again. What goes in the containers is summarised in collections[].contents when present. If contents is null, say the council has not published contents in the evidence held; never guess from colour or name. accepted combines council labels across containers: use appearance_occurrences items for each container and condition, especially when varies_by_date is true. Rules: never guess or choose a property