Skip to main content
Glama

Vizo: out-of-home advertising in Paraguay and Uruguay

Solicitar cotización a Vizo

solicitar_cotizacion

Envía a Vizo un pedido de cotización (precio y disponibilidad) de uno o más espacios para unas fechas. No cobra nada: Vizo responde por email. Usar SOLO después de mostrar al usuario los espacios, las fechas y sus datos, y con su confirmación explícita.

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": {
      "ids": "<ids>",
      "desde": "<desde>",
      "hasta": "<hasta>",
      "nombre": "<nombre>",
      "email": "<email>",
      "whatsapp": "<whatsapp>",
      "confirmado_por_el_usuario": "<confirmado_por_el_usuario>"
    },
    "name": "solicitar_cotizacion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesids de los espacios (máx. 15)
desdeYesFecha de inicio AAAA-MM-DD
emailYes
hastaYesFecha de fin AAAA-MM-DD
nombreYesNombre de la persona o empresa
mensajeNoComentario opcional (marca, objetivo, presupuesto)
whatsappYesWhatsApp con código de país, ej. 595981123456
confirmado_por_el_usuarioYestrue solo si el usuario confirmó explícitamente el envío

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds two things they do not: that no charge occurs and that the response arrives asynchronously by email rather than as a synchronous result. It does not cover failure behavior, retry/idempotency or rate limits, so it stops short of a 5.

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 short sentences with zero filler: purpose first, cost/response channel second, gating condition last. Every sentence carries information the agent needs.

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 an 8-parameter submission tool with no output schema, the description explains the response channel (email), the absence of payment and the confirmation requirement, which is close to complete. The remaining gap is what the caller receives immediately on success or failure.

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 88%, so the schema already explains ids, desde/hasta format, whatsapp country code and the confirmation flag. The description only adds context that the ids refer to 'espacios' and that contact data is required, which is marginal over the structured fields.

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 ('Envía a Vizo un pedido de cotización (precio y disponibilidad) de uno o más espacios para unas fechas') and immediately bounds it ('No cobra nada'), which separates it from the read-only search sibling tools without naming them. An agent knows this requests a price/availability quote, not a booking.

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?

Gives an explicit, testable precondition: use ONLY after showing the user the spaces, dates and their data, and only with explicit confirmation. That is a when-to-use gate plus a when-not-to-use prohibition, and it aligns with the required confirmado_por_el_usuario flag.

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