Skip to main content
Glama

Live pollen measurements

get_pollen
Read-only

Retrieve live hourly pollen concentrations from the official MeteoSwiss monitoring network by taxon, and optionally sort stations by distance from a latitude/longitude to find nearby readings.

Instructions

Live hourly pollen concentrations from the official MeteoSwiss pollen monitoring network. Choose a taxon (grasses, birch, ash, alder, hazel, mugwort, ambrosia); optionally sort stations by distance from a point (pass both near_lat and near_lon).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
taxonNoPollen taxon: graeser=grasses, birke=birch, esche=ash, erle=alder, hasel=hazel, beifuss=mugwortgraeser
near_latNoOptional: WGS84 latitude (requires near_lon)
near_lonNoOptional: WGS84 longitude (requires near_lat)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and does add useful context: data is 'live' and 'hourly' and comes from an official MeteoSwiss network, which tells the agent about freshness and authority. It does not disclose geographic coverage limits (presumably Switzerland), concentration units, station record shape, or caching/refresh behavior, which are the traits an agent would still want.

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 sentences, front-loaded with the resource and source, then the configuration guidance. No filler, no restatement of the title, and the parenthetical enumerations are compact.

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 four-parameter read-only lookup with no output schema and low complexity, the description covers source, cadence, selection, and the optional geo-sorting. Remaining gaps (units, geographic scope, number of stations returned) are minor for a tool this simple, though an agent would still have to open the schema to learn the default and maximum for limit.

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 75%, and the description adds meaning the schema does not: near_lat/near_lon are used to *sort stations by distance from a point*, not to filter them, which is a materially different semantic from what the bare coordinate descriptions convey. It also restates the taxon enum mapping and the pairing requirement, but leaves the limit parameter unaddressed.

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 first sentence gives a specific verb+resource+source: 'live hourly pollen concentrations from the official MeteoSwiss pollen monitoring network.' It is unambiguous what the tool returns and where it comes from. It stops short of naming a sibling or stating a scope boundary (e.g. vs. a general air-quality or current-measurements tool), so it is clear but not differentiated.

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?

'Choose a taxon ...; optionally sort stations by distance from a point' tells the agent how to configure a call, which implies the use case. There is no explicit statement of when to prefer this tool over alternatives, nor any when-not guidance, so usage is implied rather than prescribed.

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