Skip to main content
Glama

glosa_explain

Read-only

Explica um código da Tabela 38 da ANS. Quando usar: ao interpretar uma glosa recebida. Quando não usar: para validar ou corrigir o lote.

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": {
      "codigo": "<codigo>"
    },
    "name": "glosa_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYes

Output Schema

NameRequiredDescriptionDefault
fonteYes
grupoYes
codigoYes
descricaoYes
orientacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety and locality profile is covered structurally. Note that openWorldHint=false sits slightly in tension with looking up an external ANS table, but the description does not contradict the annotation outright. The description adds the domain context (Tabela 38, glosa interpretation) but nothing about failure behavior when a code is unknown, and the output schema covers returns.

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?

Two short sentences plus a labeled when-to-use / when-not-to-use pair, front-loaded with the core purpose. Nothing is redundant and the structure is immediately scannable.

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 one-parameter read-only lookup with an output schema and full annotations, the description covers purpose, trigger and exclusion adequately. The only real gap is behavior on an unknown or invalid code, which would help an agent decide how to react to a lookup miss.

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?

The single parameter has 0% schema description coverage, so the schema alone only shows a four-digit regex. The description compensates by identifying the code as a Tabela 38 ANS code used in glosa interpretation, which is real added meaning. It still does not explain what a valid code domain looks like or what happens outside it.

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

Purpose4/5

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

The description uses a specific verb ('Explica') with a specific resource ('um código da Tabela 38 da ANS'), so the agent knows exactly what is being looked up. Sibling differentiation is partial: it says the tool is not for validating or correcting a batch, which implicitly points away from tiss_validate / tiss_apply_fixes, but no sibling is named.

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?

It gives an explicit 'quando usar' (interpreting a received glosa) and an explicit 'quando não usar' (validating or correcting the batch), which is stronger guidance than most definitions. It stops short of a 5 because the alternative tools are described only by category rather than named, leaving the agent to map 'validar o lote' onto the right sibling.

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.