Skip to main content
Glama

Opensensemap Box

opensensemap_box
Read-onlyIdempotent

Get one openSenseMap citizen science sensor station (senseBox) by its box id, full sensor readout with latest value, unit, and measurement time per sensor (temperature, humidity, PM2.5/PM10 air quality, pressure, noise...), plus location, exposure (outdoor/indoor/mobile) and station metadata. Box ids come from opensensemap_nearby. Community-operated uncalibrated sensors. Example: opensensemap_box({ box_id: "65e8d93acbf5700007f920ca" })

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": {
      "box_id": "65e8d93acbf5700007f920ca"
    },
    "name": "opensensemap_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
box_idYes24-char openSenseMap box id, e.g. "65e8d93acbf5700007f920ca"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "box_id": "65e8d93acbf5700007f920ca"
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower, but the description still adds real context: it discloses what the return payload contains field-by-field and warns 'Community-operated uncalibrated sensors', a data-quality caveat that the annotations cannot convey. It does not cover failure behavior for an invalid or nonexistent box id, which is the main remaining gap for a lookup tool.

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?

Front-loaded with the verb and resource, then the payload contents, then the id source and caveat — a sensible order with no filler sentences. The inline example duplicates the schema's examples field, a small redundancy, but the rest of the text is dense with information.

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 one required parameter, full schema coverage, and rich annotations, the description is nearly sufficient: it explains the payload and the uncalibrated-sensor caveat despite no output schema being present. Missing only edge-case behavior such as what happens with an unknown box id.

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 already states the 24-character id format with an example, so parameter meaning is essentially fully documented upstream. The description adds only provenance ('Box ids come from opensensemap_nearby'), which is useful but marginal, so the baseline 3 applies.

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?

Uses a specific verb and resource ('Get one openSenseMap citizen science sensor station (senseBox) by its box id') and immediately enumerates what comes back: per-sensor latest value, unit, measurement time, plus location, exposure and metadata. It also distinguishes itself from the sibling list-only tool by noting box ids come from opensensemap_nearby, so an agent can separate this single-station lookup from nearby/area_average calls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line 'Box ids come from opensensemap_nearby' gives an explicit prerequisite and effectively routes the agent to the discovery tool first, which is the main selection decision for this tool. There is no explicit when-not-to-use statement (e.g. use area_average for aggregated values), so it falls short of full alternative coverage.

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.