Skip to main content
Glama

Bettiz Legal — guías legales (Chile)

Cómo agendar una cita

how_to_book
Read-onlyIdempotent

Las citas se agendan solo por WhatsApp (+56 9 9489 7327); el diagnóstico se paga antes y su valor se informa al agendar. Horario, oficina y atención en línea.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety needs no restating. The description still adds genuinely new behavioral context: bookings happen exclusively through WhatsApp at a specific number, the diagnostic must be paid before booking, and the price is only revealed at booking time rather than returned here.

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?

One dense sentence that front-loads the decisive constraint (WhatsApp-only booking with the number) before payment terms and logistics. No filler and nothing that could be cut without losing a real constraint.

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 zero-parameter, no-output-schema informational tool, this covers the channel, the payment order, where the price comes from, and the location/format of service (hours, office, online). It is close to complete for the agent's needs, though it does not say whether the returned text is the instructions themselves or a redirect.

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 takes no parameters, so the baseline applies and there is nothing for the description to clarify. The description correctly refrains from inventing inputs and instead frames the answer as fixed policy information.

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 makes clear this tool answers 'how do I book an appointment', naming the concrete channel (WhatsApp with a phone number) and the payment precondition. It is a specific informational resource rather than a vague restatement of the name. It stops short of explicitly contrasting with siblings like get_page or list_services.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and content: call this when the user asks how to schedule. There is no explicit when-to-use/when-not-to-use statement or pointer to an alternative sibling if the user actually wants service listings or general page content. Minimum viable guidance.

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