Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_waste_collection_schedule

Get upcoming municipal 4-stream household waste collection dates (Restmüll, Biomüll, Altpapier, Gelber Sack / Wertstoff).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_waste_collection_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
waste_typeNoOptional stream filter: Restmüll, Biomüll, Papier, or Gelber Sack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it omits critical facts: how the municipality is resolved given the only parameter is a stream filter, how far ahead 'upcoming' reaches, and whether results cover one household or a general feed. Only the stream enumeration adds value.

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?

One front-loaded sentence with zero filler; the resource and its scope come first, and the parenthetical enumeration is compact and informative.

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

Completeness2/5

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

For a read tool with no annotations and no output schema, the description should explain how the location context is supplied and what the returned dates look like. Neither is covered, leaving a genuine gap for an agent that must decide whether this tool is usable for its user's address.

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 100% and the single parameter is optional, so the schema already does the work; baseline 3 applies. The description restates the stream names but uses 'Altpapier' where the schema says 'Papier', a minor naming mismatch that could cause ambiguity without adding real meaning.

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

Purpose5/5

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

States a specific verb ('Get') plus a precisely scoped resource ('upcoming municipal 4-stream household waste collection dates') and enumerates the streams covered. No sibling tool shares this domain, so an agent can identify the right tool immediately.

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 only implied by the domain phrasing; there is no statement of when to prefer this tool, no exclusions, and no mention of prerequisites. The key operational question of which municipality/address the dates apply to is never addressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources