Skip to main content
Glama
geobr-mcp

geobr-mcp

rbmc_mais_proximas

Finds RBMC GNSS stations near a coordinate, ordered by distance, with azimuth, recent status, receiver details, and practical RTK, static, or PPP guidance.

Instructions

Estações GNSS da RBMC (IBGE) mais próximas de uma coordenada: distância, azimute, situação na última semana, receptor e link do descritivo, com orientação prática (RTK, estático, PPP).

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "rbmc_mais_proximas"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
so_ativasNo
quantidadeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description has to carry the full load: it does disclose the returned fields and that status reflects 'the last week' (a useful recency window). It does not state that the operation is a non-mutating lookup, which datum/coordinate system lat/lon must be expressed in, or what happens when no station meets the criteria — notable gaps given sibling datum-transformation tools that imply reference-frame ambiguity.

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 dense sentence with the resource and coordinate scope front-loaded, then the return payload. Every clause contributes; only the sub-list of fields makes it slightly listy, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description partly compensates for the missing output schema by naming the returned fields, but with no annotations, no output schema, and three undocumented optional parameters (including a boolean filter and a count), an agent still lacks the coordinate format and result-limit behavior needed to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the 4 parameters are undocumented: the description only alludes to 'uma coordenada' without saying lat/lon are strings in decimal degrees, and never explains so_ativas (default true, presumably filtering to operational stations) or quantidade (default 3, result count). With the schema doing nothing, the description should have compensated and does not.

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 resource (RBMC/IBGE GNSS stations) and the exact operation (nearest to a coordinate), and enumerates what comes back: distance, azimuth, weekly status, receiver, descriptive sheet link, and practical RTK/static/PPP guidance. No sibling tool in the list does station lookup, so the agent can route here without ambiguity.

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?

The mention of 'orientação prática (RTK, estático, PPP)' implies the surveying use case but never says when to pick this tool, what the prerequisites are, or what to do if results are empty. Since no sibling overlaps, the absence of an explicit alternative is tolerable, leaving usage implied rather than stated.

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