Skip to main content
Glama

Tirar dúvida sobre a consulta online

tirar_duvida
Read-onlyIdempotent

Returns Doutor Chamada's official answers (the same as the FAQ on the website) for one topic: how it works, medical certificates, prescriptions, exams, documents, payment and refunds, children and family, safety and data protection, and when not to use telemedicine. Use to answer questions about the service accurately. The only input is the topic.

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": {
      "tema": "<tema>"
    },
    "name": "tirar_duvida"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaYescomo-funciona = how it works, waiting time, video, hours, app; atestado = medical certificates (sick notes); receitas = prescriptions and renewals; exames = exam requests; documentos = receiving and fixing documents; pagamento = price, payment methods, refunds; familia = children and family; seguranca = trust, data protection, document validation; emergencias = when NOT to use telemedicine.

Output Schema

NameRequiredDescriptionDefault
temaYes
avisosYes
tituloYes
perguntasYes
emergenciaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds meaningful context beyond that: the answers are authoritative and identical to the website FAQ, which tells the agent this is a trustworthy canonical source rather than generated content. It says nothing about freshness or answer length, but an output schema exists to cover the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what the tool returns, followed by when to use it and the input shape. The prose topic list partially duplicates the enum descriptions in the schema, which is the only redundancy, but it serves as a quick scannable scope summary.

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 required enum parameter with an output schema and rich annotations, the description covers purpose, provenance of the answers, and usage context. Nothing essential is missing; only a note on how to handle out-of-scope questions would make it fully self-contained.

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 enum values each carry their own explanation, so the schema does the heavy lifting. The description restates the topic categories in prose ('how it works, medical certificates, prescriptions...') and notes the topic is the only input, which is mildly reinforcing but adds no semantics the schema does not already provide.

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?

The description states a specific verb and resource — returns the service's official FAQ answers for one topic — and enumerates the topic space so the agent knows exactly what content it can retrieve. It is unmistakably distinct from the sibling action tools (iniciar_consulta, listar_opcoes_de_consulta, verificar_plantao), which start or inspect consultations rather than answer questions.

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 a clear triggering condition: 'Use to answer questions about the service accurately', plus a topic list that tells the agent which questions are in scope. It stops short of explicit exclusions or naming sibling tools to use instead when the question is really a booking request, so it is clear but not fully routing-aware.

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