Skip to main content
Glama

Opensensemap Area Average

opensensemap_area_average
Read-onlyIdempotent

Average one phenomenon across all citizen science sensors (openSenseMap / senseBox network) in an area, hyperlocal neighborhood-level temperature, PM2.5/PM10 air quality, humidity, pressure or noise from many independent community stations. Give either a bounding box or a center point + radius_km. Aggregates the latest reading per sensor over the recent window client-side (the network has no fast server-side aggregation). Phenomenon names on openSenseMap are mostly German (exact sensor titles): "Temperatur" (temperature °C), "rel. Luftfeuchte" (relative humidity %), "Luftdruck" (air pressure hPa), "PM2.5" and "PM10" (particulate matter µg/m³), "Beleuchtungsstärke" (illuminance lx), "UV-Intensität" (UV µW/cm²), "Lautstärke" (noise)the name must match the sensor title exactly (e.g. "Temperatur", not "temperature"). Example: opensensemap_area_average({ phenomenon: "PM2.5", latitude: 52.52, longitude: 13.405, radius_km: 5 })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": 52.52,
      "longitude": 13.405,
      "radius_km": 5,
      "phenomenon": "PM2.5"
    },
    "name": "opensensemap_area_average"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNoBounding box as "west,south,east,north" in degrees, e.g. "13.3,52.45,13.5,52.55" (overrides center+radius)
latitudeNoCenter latitude (use with longitude + radius_km, instead of bbox)
longitudeNoCenter longitude
radius_kmNoRadius in km around the center, 0.1-25 (default 5)
phenomenonYesExact phenomenon / sensor title, e.g. "PM2.5", "PM10", "Temperatur", "rel. Luftfeuchte", "Luftdruck", "Lautstärke"
window_hoursNoHow far back to look for each sensor's latest reading, 1-24 hours (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "latitude": 52.52,
      +    "longitude": 13.405,
      +    "phenomenon": "PM2.5",
      +    "radius_km": 5
      +  },
      +  {
      +    "bbox": "13.3,52.45,13.5,52.55",
      +    "phenomenon": "Temperatur",
      +    "window_hours": 2
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing that aggregation happens client-side because the network lacks fast server-side aggregation, and that only each sensor's latest reading within a recent window is included. It also warns that phenomenon titles are mostly German and must match sensor titles exactly, a real failure mode. This is exactly the kind of non-obvious behavior an agent needs.

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

Conciseness3/5

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

The key scoping information is front-loaded, but the body is a dense run-on with a formatting defect where "(noise)the name must match" runs together, hurting readability. The trailing example call also duplicates the examples already present in the input schema, so not every sentence earns its place.

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?

With no output schema, the description covers inputs, phenomenon naming, aggregation method and freshness window thoroughly, which is most of what is needed. It stops short of describing the response shape (e.g. average value, contributing sensor count) or what happens when too few sensors match, which is the remaining gap for a no-output-schema tool.

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 already 100%, so baseline is 3; the description adds meaning by giving the exact German title strings with units for each phenomenon and stressing exact match ("Temperatur", not "temperature"), plus a concrete example call. It largely restates the bbox-override and default radius/window behavior already in the schema, keeping it off a 5.

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?

States a specific verb and resource: averages one phenomenon across all citizen science sensors in an area, naming the openSenseMap/senseBox network and the supported quantities (temperature, PM2.5/PM10, humidity, pressure, noise). The area-wide, multi-station scope implicitly distinguishes it from the single-box and nearby-box siblings, but it never names them, so an agent must infer the routing.

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?

Explains the two geographic input modes (bbox vs. center + radius_km) and the recent-window aggregation, which is usable context. However, it never says when to prefer this over opensensemap_box or opensensemap_nearby, and gives no exclusions or prerequisites (e.g. sparse sensor coverage), leaving the agent to infer the choice.

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.