Skip to main content
Glama
SUS healthcare MCP
by bnovarini

geographic_signals

Retrieve fixed annual municipal diagnosis activity intervals by state and year from Brazil's public healthcare data, returning aggregate counts with small cells omitted and no patient records.

Instructions

Fixed annual municipal diagnosis activity intervals, not patients. Small cells omitted.

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": {
      "uf": "<uf>",
      "year": "<year>"
    },
    "name": "geographic_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufYes
yearYes
limitNo
familyNoRD
cid_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that small cells are omitted and that the unit is activity intervals rather than patients, but it says nothing about permissions, query behavior, defaults, pagination, or result format.

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 description is compact and front-loaded, with no wasted sentences, but its terseness comes at the cost of clarity rather than being optimally informative. It is appropriately brief for a short definition but under-explains the tool.

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

Completeness2/5

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

For a five-parameter query tool with no annotations and no output schema, the description is far too thin. It gives one important caveat about small-cell suppression but leaves usage, parameters, and expected output largely unexplained.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no information about any of the five parameters (uf, year, limit, family, cid_prefix). The parameter meanings are left entirely to the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a domain resource ('annual municipal diagnosis activity intervals') and distinguishes it from patient-level data, but it never states a clear action such as 'retrieve' or 'list' and remains ambiguous about what the tool actually returns. An agent cannot confidently tell from this text what geographic_signals does beyond producing some activity-interval aggregation.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus siblings such as fixed_proxy_activity or ecological_hits. The phrase 'not patients' hints at a unit-of-analysis distinction, but no alternatives or exclusion conditions are named.

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