Skip to main content
Glama

Começar a consulta no site

iniciar_consulta
Read-onlyIdempotent

Returns the website link to start a video consultation with Doutor Chamada for the chosen option, with the step-by-step (sign up and pay on the website, then wait for the doctor on video), the current on-call status and the emergency notice. Use when the person wants to start a consultation. The only input is the option; never send symptoms or personal data. The tool does not assess symptoms; for an emergency, tell the person to call 192 instead.

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": "iniciar_consulta"
  }
}

Input Schema

NameRequiredDescriptionDefault
opcaoNoclinico_geral = adult (18+) general practitioner; crianca = patient under 18, the parent or guardian signs up; aptidao_fisica = sports and fitness clearance (gym, pool, running, sports federation); taf = physical fitness test for a public-service exam (concurso); estrangeiro = foreigner in Brazil without a CPF (signs up with a passport). If you do not know whether the patient is an adult or a child, ask first; otherwise use clinico_geral.clinico_geral

Output Schema

NameRequiredDescriptionDefault
avisoYes
ofertaYes
passosYes
plantaoYes
disponivelYes
documentosYes
emergenciaYes
quemAvaliaYes
identificacaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it as a safe, idempotent read; the description goes well beyond them by disclosing the actual user journey (sign up and pay on the website, then wait for the doctor on video), that on-call status is included, and that an emergency notice is attached. It also states a hard privacy constraint ('never send symptoms or personal data'), which is behavioral guidance no annotation could convey.

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 sentences, front-loaded with the return value and the trigger, with no filler. The first sentence is long and packs the response contents into a single clause, which is dense but still readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarizes the payload (link, steps, on-call status, emergency notice) so the agent knows what it will get. Combined with the emergency fallback and the privacy constraint, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum values are already documented in detail, so the schema does the heavy lifting. The description still adds value by declaring the option is the 'only input' and by imposing a negative constraint on what must not be sent, which the schema cannot express.

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 uses a concrete verb+resource ('Returns the website link to start a video consultation with Doutor Chamada'), and then enumerates exactly what the response carries: step-by-step flow, on-call status and the emergency notice. It also draws a scope boundary ('does not assess symptoms'), which separates it from a question-answering sibling like tirar_duvida.

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?

'Use when the person wants to start a consultation' gives an explicit trigger, and the emergency clause gives an explicit when-not (route to 192 instead). The remaining gap is that it never names an alternative tool by name, so an agent that receives a vague request must infer the routing itself.

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