Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_pollen_allergy_index

Retrieve official Deutscher Wetterdienst (DWD) 8-allergen pollen load (birch, grass, hazel, alder, ragweed, mugwort, rye, ash) and PM2.5/Ozone air quality.

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_pollen_allergy_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundeslandNoGerman state (e.g. Bayern, Berlin, Nordrhein-Westfalen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It establishes provenance (official DWD data) and the data categories returned, which is useful, but it never says whether values are forecast or current measurements, how fresh they are, or what happens when the optional state is omitted (national aggregate vs. error).

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?

One front-loaded sentence with the verb and source first and the payload second, with no filler or repetition. The parenthetical allergen roster is long but each item adds real information about coverage, so it is only mildly verbose rather than wasteful.

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 with one optional parameter and no output schema, the description covers what is returned and from where, which is the main thing an agent needs. The remaining gaps, temporal semantics (forecast vs. observed) and default geographic scope when 'bundesland' is omitted, are the only meaningful omissions.

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% and the single optional 'bundesland' parameter is fully documented with examples in the schema, so a baseline of 3 is the floor. The description slightly exceeds that by framing the tool as German-scoped and DWD-sourced, though it never explicitly ties the parameter to regional filtering or says what the default scope is; with only one parameter and zero params required, a 4 is warranted.

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 ('Retrieve'), a named authoritative source (DWD), and enumerates exactly what is returned: eight named pollen allergens plus PM2.5/Ozone air quality. This is specific enough to separate it from weather, traffic, or civil-warning siblings without opening any schema.

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 name and the allergen list: an agent can infer this is for pollen/allergy or air-quality questions. There is no explicit when-to-use statement, no exclusion (e.g. 'for general weather warnings use get_weather_and_civil_warnings'), and no note on whether the two data types share a scope.

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