Skip to main content
Glama

operadora_rede

Read-only

Consulta os estabelecimentos vinculados a uma operadora. Quando usar: para identificar unidades da rede por UF. Quando não usar: para buscar o cadastro geral; use operadora_lookup.

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": {
      "registro": "<registro>"
    },
    "name": "operadora_rede"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
limiteNo
registroYes

Output Schema

NameRequiredDescriptionDefault
fonteYes
totalYes
por_ufYes
registro_ansYes
atualizado_emYes
estabelecimentosYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds only a filtering-scope hint ('por UF') and no behavioral context beyond that, such as result ordering or what happens when no network matches. With annotations carrying the load, a baseline 3 is appropriate.

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 short clauses with no filler: purpose first, then when-to-use, then the exclusion plus the named alternative. Nothing could be dropped without losing routing 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?

An output schema exists, so return values need no explanation, and the routing guidance is complete. The remaining gap is the undocumented 'limite' paging parameter for a list tool, which the agent would have to infer from the schema alone.

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 0%, so the description must compensate. It implies that uf filters the network and that registro identifies the operator, but the required 'registro' is never explained by name and 'limite' (default 200, max 1000) is not mentioned at all. Partial compensation only.

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 verb and resource: 'Consulta os estabelecimentos vinculados a uma operadora'. The scope (network units tied to one operator) is distinct from the general-registry sibling, so an agent can differentiate it without opening a schema.

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

Usage Guidelines5/5

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

Explicitly gives both directions: 'Quando usar: para identificar unidades da rede por UF' and 'Quando não usar: para buscar o cadastro geral; use operadora_lookup'. The alternative is named along with the condition that selects it.

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.