Skip to main content
Glama

Roberto Guanaes — Fisioterapia e Quiropraxia

Gerar link de WhatsApp da clínica

link_whatsapp
Read-only

Gera o link wa.me com mensagem pré-preenchida para falar com a clínica pelo WhatsApp. Entrega o link para o usuário clicar — este servidor não envia mensagem, não marca horário e não coleta dados.

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_whatsapp"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextoNoAssunto da conversa, para já escrever a mensagemavaliacao
mensagemNoTexto adicional do usuário, reescrito em primeira pessoa

Output Schema

NameRequiredDescriptionDefault
urlYes
telefoneYes
instrucaoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as readOnly, non-destructive and closed-world, so safety is covered structurally; the description adds genuinely new behavioral information — that the server sends no message itself, performs no booking, and stores no user data, and that the deliverable is a link the user must click. It does not discuss link expiry or reuse, but the side-effect contract is unusually explicit.

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, no filler. The positive capability comes first and the negative boundary clause follows immediately, which is the right order for an agent deciding whether to call it.

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?

For a two-optional-parameter, side-effect-free link generator with an output schema and full annotation coverage, nothing material is missing: the agent knows what it produces, who consumes it, and what it will not do.

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 both parameters carry their own descriptions plus an enum with a default, so the schema does the semantic work. The description adds nothing about how 'contexto' shapes the generated message or how 'mensagem' is rewritten, which would have been the one place to add meaning beyond the schema.

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 precise verb and resource — 'Gera o link wa.me com mensagem pré-preenchida' — and immediately bounds the scope by naming three things it does NOT do (send messages, book appointments, collect data), which is exactly the boundary that separates it from siblings like link_agendamento and info_clinica. An agent can classify this tool without opening the schema.

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?

The description makes the use case clear (contacting the clinic via WhatsApp with a pre-filled message) and excludes near-miss cases by stating it does not schedule appointments. It stops short of naming the sibling an agent should call instead for booking or information, so routing is implied rather than explicit.

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