Skip to main content
Glama

Ver precio, depósito y términos

ver_terminos
Read-only

Para una casa y unas fechas: total en USD, depósito de garantía en CUP, política de cancelación, horas de entrada y salida y normas de la casa. Es el texto exacto que el cliente tiene que aceptar antes de pedir. ENSÉÑASELO ENTERO al usuario antes de llamar a pedir_reserva.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "casa": "<casa>",
      "llegada": "<llegada>",
      "salida": "<salida>",
      "personas": "<personas>"
    },
    "name": "ver_terminos"
  }
}

Input Schema

NameRequiredDescriptionDefault
casaYes
salidaYes
llegadaYes
personasYes

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 read-only and closed-world behavior, while the description adds important context: the result is the exact text the customer must accept and must be shown in full before booking. It still does not describe authentication, rate limits, or response structure beyond the listed fields.

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 front-loaded with returned fields and ends with a direct, capitalized action instruction. Every sentence adds useful scope or workflow information with no filler.

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

Completeness3/5

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

It adequately describes the returned terms and the required user-facing workflow, which is important because no output schema exists. However, with four required parameters and no schema descriptions, it leaves the personas parameter and input formats unexplained.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only implies casa, llegada, and salida and omits the required personas parameter entirely. It also gives no format guidance for dates or house identifiers.

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?

States specifically that it returns total in USD, deposit in CUP, cancellation policy, check-in/out times, and house rules for a house and dates. This clearly distinguishes it from browsing or booking siblings by framing it as the exact acceptance text needed before requesting.

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

Usage Guidelines5/5

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

Explicitly tells the agent to show the entire text to the user before calling pedir_reserva, giving a clear workflow prerequisite and ordering relative to booking. It does not need to enumerate every sibling because the usage condition is precise.

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