Skip to main content
Glama
Sign In

mugilu

by io.github.sathya-sankaran
OverviewDiscussionsAdmin

nearest_stations

Read-onlyIdempotent

The nearest real (measured) air-quality monitoring stations to a place, with distance and current AQI. Use to judge how close hard measurement is. Conditions can be modelled when no station is near.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place": "<place>"
    },
    "name": "nearest_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoHow many stations (default 5).
placeYesA place name or "lat,lon" in India.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description's job is to add result semantics, which it does: only real measured stations, results carry distance and current AQI. It hints at the empty/near-empty case ('when no station is near') but doesn't state outright what is returned then, leaving a small gap.

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?

Three tight sentences, front-loaded with the identity of the tool and followed by use guidance and the fallback case. No filler and no repetition of the schema.

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 two-parameter read tool with annotations and no output schema, the description covers what it returns (distance, current AQI) and when to reach for it. Only the shape of an empty result when no station is nearby is left under-specified.

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 coverage is 100% and both parameters are fully described there, including the n default and maximum plus the 'lat,lon' place format. The description only echoes 'to a place' and adds no syntax or filtering detail beyond the schema, 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?

The description gives a precise verb and resource: the nearest real, measured air-quality monitoring stations to a place, returned with distance and current AQI. The contrast with modelled conditions ('real (measured)', 'Conditions can be modelled when no station is near') tells an agent exactly how this differs from the modelled-conditions siblings without needing their schemas.

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?

'Use to judge how close hard measurement is' states the use case clearly, and the closing clause gives the fallback condition when no station is near. It stops short of naming the specific alternative tool for modelled conditions, so the routing is implied rather than explicit.

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

All mugilu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources