Skip to main content
Glama

Roberto Guanaes — Fisioterapia e Quiropraxia

Link de agendamento, formulário e como chegar

link_agendamento
Read-only

Retorna os links oficiais de contato (página de contato com formulário), localização no Google Maps e rota até a clínica. Use quando o usuário quiser agendar por formulário, ver o endereço no mapa ou se deslocar até o consultório.

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

Input Schema

NameRequiredDescriptionDefault
destinoNocontato = formulário; maps = perfil no Maps; rota = como chegarcontato

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 and side-effect profile is fully covered. The description adds only that the links are "oficiais" and what each one points to — no detail on response shape, whether URLs are static or session-bound, or failure behavior. Useful but modest added context given the annotation coverage.

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?

Two sentences with no filler: the return content comes first, followed by the selection guidance. Slight redundancy between the title and the enumeration of links keeps it from being maximally tight.

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?

The tool is simple — one optional enum parameter, no output schema — and the description explains the three possible outputs well enough for correct invocation. It does not specify the return format (single link vs. text block), which is the only meaningful gap for a tool with no output schema.

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% with a single enum parameter whose values are already documented inline. The description reinforces what each value yields (formulário, perfil no Maps, como chegar), which matches the schema rather than extending it, so the baseline of 3 applies.

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 ("Retorna") and names the three concrete resources returned: contact page with form, Google Maps location, and route to the clinic. The purpose is unmistakable, though it never mentions the sibling link_whatsapp, so the agent must infer that WhatsApp contact is a separate tool.

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?

Explicitly maps usage conditions to each mode: "quando o usuário quiser agendar por formulário, ver o endereço no mapa ou se deslocar até o consultório." That is clear when-to-use guidance, but it offers no exclusion telling the agent to prefer link_whatsapp for messaging contact.

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