Skip to main content
Glama

Roberto Guanaes — Fisioterapia e Quiropraxia

Sinais de alerta e quando procurar avaliação

quando_procurar_avaliacao
Read-only

Dado um conjunto de sintomas descritos pelo usuário, retorna os sinais de alerta (red flags) publicados pelo site e se há indicação de avaliação médica urgente. NUNCA diagnostica nem indica tratamento; serve para encaminhar com segurança.

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": {
      "sintomas": "<sintomas>"
    },
    "name": "quando_procurar_avaliacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
sintomasYesSintomas como a pessoa descreveu, ex.: ['travei a lombar', 'dor desce para a perna']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 structurally. The description adds genuinely useful behavioral context: results come from site-published red flags, output includes an urgency indication, and the tool deliberately withholds diagnosis and treatment advice. It stops short of describing result shape or what happens on an unmatched symptom set.

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 padding. The input-to-output contract comes first and the critical safety disclaimer is front-loaded with emphasis in the second sentence.

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 read-only, single-parameter tool with no output schema, the description covers input expectation, return content and the diagnostic boundary. Only the granularity of the returned red-flag/urgency payload is left unstated, which is acceptable since no output schema exists to defer to.

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 100% and the single 'sintomas' parameter already carries type, bounds, limits and a worked example, so the description cannot add much. Its phrase 'sintomas descritos pelo usuário' usefully reinforces that entries should be verbatim lay phrasing rather than clinical terms, but that is a marginal gain.

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?

States a specific verb and resource: given user-described symptoms, it returns site-published red flags plus whether urgent medical evaluation is indicated. That is concrete enough for an agent to know exactly what comes back, though it does not name which sibling (info_clinica, buscar_conteudo) to prefer for non-urgent content.

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 trigger condition is implied by 'Dado um conjunto de sintomas descritos pelo usuário', and the 'NUNCA diagnostica' clause marks the boundary of what it will answer. However, it never says when to reach for this versus info_clinica or buscar_conteudo, nor what to do when no red flags match.

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