Skip to main content
Glama

Preparar cotización

prepare_quote
Read-onlyIdempotent

Arma el mensaje de una solicitud de cotización para Kroel Graphics. Úsala cuando la persona ya decidió pedir precio y tienes su nombre y su idea. Devuelve el texto del mensaje y un enlace de WhatsApp con ese texto ya escrito. No envía nada: la persona debe abrir el enlace y confirmar el envío.

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": {
      "nombre": "<nombre>",
      "idea": "<idea>"
    },
    "name": "prepare_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesDescripción del proyecto.
fechaNoFecha de entrega deseada.
nombreYesNombre de quien solicita.
serviciosNoServicios que necesita (nombres de get_services).
presupuestoNoPresupuesto aproximado (opcional).

Output Schema

NameRequiredDescriptionDefault
notaNo
enlaceYesEnlace de WhatsApp con el mensaje escrito.
mensajeYesTexto de la solicitud.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: it returns message text plus a pre-filled WhatsApp link, and it performs no send — the person must open the link and confirm. That human-in-the-loop detail is exactly what an agent needs to avoid assuming delivery happened.

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?

Three sentences, front-loaded with the core action, then the usage trigger, then the return value and the safety caveat. No filler; each sentence carries distinct information.

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?

Despite an output schema existing, the description usefully summarizes the return (text plus link) and clarifies that no send occurs. For a read-only preparation tool with five parameters, nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3. The description reinforces that nombre and idea are the inputs needed, but adds no semantics for fecha, servicios, or presupuesto beyond what the schema already documents.

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 a specific verb and resource: 'Arma el mensaje de una solicitud de cotización'. It is explicitly distinguished from its sibling send_quote_request by the closing clause 'No envía nada', so an agent can tell preparation from sending without opening either 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?

'Úsala cuando la persona ya decidió pedir precio y tienes su nombre y su idea' gives a clear trigger condition and matches the two required parameters. The exclusion is implied through the no-send clause rather than stated as a named alternative, so it stops just short of full when-not 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.