Skip to main content
Glama

get_waste_calendar

Read-onlyIdempotent

Fetch the monthly waste collection calendar for a Zurich ZIP code (8001–8099) by year and month, defaulting to the current month. Use it to check pickup dates for OpenERZ waste schedules.

Instructions

Monthly waste collection calendar 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_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYese.g. 8004
yearNodefault: current year
monthNo1–12, default: current month

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / month / description
      Previous value: -"Month number (1–12). Defaults to the current month."New value: +"1–12, default: current month"
    • changedInput schema / properties / year / description
      Previous value: -"Year (e.g. 2026). Defaults to the current year."New value: +"default: current year"
    • 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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds useful scoping context (Zurich-only, ZIP 8001–8099, OpenERZ data source) but says nothing about the return shape, coverage gaps in the calendar, or behavior for out-of-range ZIPs. Adds value, but modest given the annotation coverage.

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?

Two compact sentences, zero filler, with the resource and the geographic constraint front-loaded. Nothing in the text is redundant or restated.

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 three-parameter read tool with full schema coverage and no output schema, the definition covers purpose, geography and data source adequately. The only gap is any hint about the calendar's shape or whether coverage is complete for all Zurich ZIPs, which is minor.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely new constraint information the schema lacks: valid ZIP values are limited to 8001–8099 (the schema only shows 'e.g. 8004'). Year/month defaulting and the 1–12 range are already in the schema, so no further credit there.

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?

Names a specific resource (monthly waste collection calendar) keyed to a ZIP code, which is concrete and distinguishable from a generic waste lookup. It does not explicitly differentiate itself from siblings like get_waste_collection or list_waste_types, so sibling separation is left implicit.

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 geographic constraint 'Zurich city only (8001–8099)' effectively tells an agent when this tool is valid, which is real usage guidance. However, there is no explicit statement of when to prefer it over the sibling waste tools or what to do outside the ZIP range.

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