Skip to main content
Glama

Roberto Guanaes — Fisioterapia e Quiropraxia

Listar tratamentos e valores de sessão

listar_tratamentos
Read-only

Lista os tratamentos da clínica com valores oficiais da tabela (avaliação, consulta com retorno, planos de sessões e reabilitação de LCA). Use quando o usuário perguntar preço, quanto custa a sessão ou quais planos existem para pessoa física. Para empresa, use calcular_plano_in_company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_tratamentos"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicoNopaciente = pessoa física; empresa = In Companypaciente

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds one useful behavioral signal, that the values are 'oficiais da tabela' (authoritative rather than approximate), but says nothing about whether inactive/removed treatments appear or how the list is ordered. Adequate, not rich.

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 sentences with no waste: the first establishes what is returned and its authoritative source, the second handles when-to-use and the alternative. Front-loaded and easy to parse.

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 single-parameter, read-only listing tool with no output schema, the description covers purpose, contents and routing sufficiently. The only gap is the unexplained 'empresa' branch of its own parameter, which the description routes elsewhere instead of clarifying.

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 description coverage is 100% and the enum is already documented inline ('paciente = pessoa física; empresa = In Company'), so the baseline of 3 applies. The description reinforces the pessoa física path but never explains what the accepted 'empresa' value of the same parameter returns, leaving a small ambiguity between the parameter's declared values and the redirect to calcular_plano_in_company.

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 ('Lista os tratamentos da clínica') and enumerates the actual contents (avaliação, consulta com retorno, planos de sessões, reabilitação de LCA). It explicitly contrasts with the sibling calcular_plano_in_company, so an agent can distinguish them without opening either 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?

Gives explicit trigger conditions ('quando o usuário perguntar preço, quanto custa a sessão ou quais planos existem') and an explicit alternative for the out-of-scope case ('Para empresa, use calcular_plano_in_company'). This is close to a routing rule rather than a hint.

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.

Resources