Skip to main content
Glama

Roberto Guanaes — Fisioterapia e Quiropraxia

Informações da clínica

info_clinica
Read-only

Retorna nome, endereço completo, telefone/WhatsApp, horários, coordenadas, credenciais (USP, CBQ, CREFITO) e links oficiais da clínica Roberto Guanaes em Ribeirão Preto. Use sempre que precisar informar contato, localização, horário ou quem atende. Não responda esses dados de memória.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that by identifying the clinic as the canonical source and enumerating the returned data, though it does not describe output format or error behavior.

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?

The description is two efficient sentences: the first front-loads what is returned, and the second gives usage guidance. Every clause earns its place without repetition or filler.

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 zero-parameter, read-only retrieval tool with no output schema, the description is complete enough: it enumerates the returned fields and tells the agent when to use it and not to rely on memory. No critical information an agent needs to invoke it 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?

The tool has zero parameters, so there are no parameter semantics to clarify. The empty input schema is consistent, and the description correctly does not waste space on parameter explanations.

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?

The description uses a specific verb and resource ('Retorna ... da clínica Roberto Guanaes em Ribeirão Preto') and enumerates the exact fields returned, so the purpose is unambiguous. It does not explicitly contrast itself with a sibling tool, which keeps it below a 5.

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 clearly states when to use the tool: whenever contact, location, hours, or who attends must be informed, and explicitly says not to answer this data from memory. It does not name when-not-to-use cases or point to alternative siblings such as link_agendamento.

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