Skip to main content
Glama

get_waste_collection

Read-onlyIdempotent

Retrieve upcoming waste collection dates for a Zurich ZIP code (8001–8099) via OpenERZ. Filter by waste type such as cardboard, paper, organic, or textile, and set a limit.

Instructions

Upcoming waste collection dates for a ZIP code. Zurich city only (8001–8099, OpenERZ)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zip": "<zip>"
    },
    "name": "get_waste_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYese.g. 8004
typeNoOmit for all
limitNomax 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of upcoming collection dates to return. Default: 5."New value: +"max 100"
    • changedInput schema / properties / type / description
      Previous value: -"Waste type to filter by (e.g. 'cardboard', 'waste', 'paper', 'organic', 'textile', 'special', 'mobile'). If omitted, returns all types."New value: +"Omit for all"
    • changedInput schema / properties / zip / description
      Previous value: -"Zurich city ZIP code (e.g. '8001', '8004', '8032'). Covers 8001–8099."New value: +"e.g. 8004"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this as a read-only, idempotent, open-world lookup. The description adds real context beyond them: the geographic eligibility range and the OpenERZ data source. It does not clarify the horizon implied by 'upcoming' or the shape of the result, which matters since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose and followed by the eligibility constraint; nothing is wasted. The parenthetical '(8001–8099, OpenERZ)' is terse but readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read lookup the essentials are present, but with no output schema the description should say what a result looks like (date plus waste type) and how far ahead 'upcoming' reaches. Those gaps leave the agent unsure about return payload expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters including the type enum and limit default. The description confirms the ZIP drives the query and implies what 'type' filters, adding marginal value on top of a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get upcoming waste collection dates) scoped to a ZIP code, which is far more informative than the bare name. However, it does not distinguish itself from the sibling get_waste_calendar or list_waste_types, so an agent must guess which one to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Zurich city only (8001–8099)' constraint effectively tells the agent when this tool is applicable and when it is not. There is no explicit guidance on choosing between this and the sibling get_waste_calendar, and no mention of what to do for out-of-range ZIPs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools