Skip to main content
Glama

Next waste collection dates

get_waste_collection
Read-only

Retrieve upcoming waste and recycling collection dates for a Zürich-region ZIP code, optionally filtered by waste type and limited in number.

Instructions

Upcoming waste and recycling collection dates for a Zürich-region ZIP code. Types: waste (household), cardboard, paper, organic (green), special, textile, metal, cargotram, etram, glass.

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
zipYesZIP code in the Zürich region, e.g. '8001'
limitNo
waste_typeNoFilter by one waste type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is provided. The description adds useful domain context, namely the regional scope and waste types, but it does not disclose pagination, ordering, error behavior, or other operational traits beyond what the annotations cover.

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

Conciseness5/5

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

The description is two tightly written sentences with the core purpose front-loaded. Every phrase earns its place, and the type list is compact and scannable.

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

Completeness4/5

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

For a simple read-only lookup tool, the description covers the essential resource, geography, and waste-type categories. The missing explanation of 'limit' and the omission of 'chipping_service' from the type list are minor gaps, because the schema still documents those details.

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

Parameters3/5

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

Schema description coverage is 67%, so the description should add meaning where possible. It explains the waste types and gives helpful parentheticals for 'waste' and 'organic', but it omits 'chipping_service' from the schema enum and does not explain the 'limit' parameter.

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?

The description states a specific resource and scope: upcoming waste and recycling collection dates for a Zürich-region ZIP code. It is clear what the tool returns, but it does not explicitly distinguish itself from potential sibling tools such as list_waste_types.

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?

Usage is implied by the phrase 'Upcoming waste and recycling collection dates for a Zürich-region ZIP code', but there is no explicit guidance on when to use this versus alternatives or when not to use it. Minimum viable context is present without exclusions.

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