Skip to main content
Glama

Enviar solicitud de cotización

send_quote_request

Envía a Luis una solicitud de cotización a nombre de una persona, con su permiso. Úsala cuando la persona ya dio su nombre, un contacto (WhatsApp o correo) y lo que necesita, y quiere que Luis le escriba. Devuelve un id, el estado "recibida" y la dirección para consultarlo. La respuesta no trae precio: Luis contesta después con la cotización exacta. Con prueba=true valida sin guardar nada.

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>",
      "contacto": "<contacto>",
      "detalle": "<detalle>"
    },
    "name": "send_quote_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoPara cuándo lo necesita.
agenteNoNombre del asistente que la envía.
nombreYesNombre de la persona que solicita.
pruebaNotrue = solo validar, sin guardar ni avisar a nadie.
detalleYesQué necesita (mínimo 10 caracteres).
contactoYesWhatsApp, teléfono o correo de la persona.
servicioNoServicio de interés (nombres de get_services).
presupuestoNoPresupuesto aproximado, si lo dio.

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes
sandboxNo
status_urlNo
recibida_enNo
siguiente_pasoNo

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 only mark this as a non-destructive, non-idempotent, closed-world write. The description adds genuinely useful behavior: the call returns an id plus status 'recibida', the response carries no price because Luis answers later, and it requires the person's permission. It does not warn that repeated calls create separate requests despite idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are front-loaded with the action and the send condition, then the return shape and the dry-run flag. Slightly long but every clause carries operational information; nothing is filler.

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?

An output schema exists, so the return explanation is partly redundant, but the caveat that no price is returned and the consent precondition are valuable. For a non-idempotent write tool, the notable remaining gap is any warning about duplicate submissions.

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 coverage is 100%, so the schema already documents all eight parameters. The description restates the required trio and the 'prueba' dry-run semantics, which largely duplicates the schema text rather than adding new meaning. Baseline 3 applies.

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 states a specific verb and resource ('Envía a Luis una solicitud de cotización a nombre de una persona') and clarifies the consent condition. It does not explicitly differentiate from the sibling 'prepare_quote', so the agent must infer the boundary between preparing and sending.

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 gives a clear precondition for use: the person has already provided a name, a contact (WhatsApp or email) and what they need, and wants Luis to write back. It also explains the 'prueba=true' dry-run path. It stops short of naming an alternative tool or stating when not to use it.

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.