Skip to main content
Glama

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

Sugerir un plan de medios

plan_de_medios
Read-only

Sugiere una combinación de espacios en una ciudad según el objetivo (marca, lanzamiento, barrio/local, promoción, evento, shopping). El precio final se confirma con solicitar_cotizacion.

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": {
      "ciudad": "<ciudad>"
    },
    "name": "plan_de_medios"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNo
ciudadYes
cantidadNoCuántos espacios proponer (1 a 15, por defecto 6)
objetivoNomarca, lanzamiento, barrio, local, promoción, evento o shopping
presupuestoNoPresupuesto aproximado con moneda, ej.: 5.000.000 PYG por quincena (informativo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that the output is a recommendation and that prices are not final, but says nothing about how many items come back or how the objective steers the mix.

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?

Two sentences, front-loaded with the core action and followed by the pricing caveat, with no filler. The parenthetical objective list partially duplicates the schema's enum values but is short enough to earn its place as a reminder.

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?

A read-only advisory tool with five parameters and no output schema; the description covers purpose and the quote handoff, which is the essential routing. It does not describe the shape of the returned plan (items per space, fields, whether prices/availability appear), which matters since no output schema exists.

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 60%: cantidad and objetivo are documented in the schema, while pais and presupuesto have no description there. The description restates the objetivo values (already in the schema) and notes city scoping, but never explains what pais or presupuesto do, leaving part of the gap unfilled.

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?

States a specific verb ('Sugiere') and resource ('combinación de espacios en una ciudad') scoped by objective, so the agent knows it returns a proposed media plan rather than raw inventory. It does not differentiate itself from siblings like buscar_espacios or comparar_espacios, which also deal with spaces.

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?

Gives clear context for use (when an objective-driven mix of spaces in a city is wanted) and explicitly routes pricing to solicitar_cotizacion, which is the most likely confusion point. It stops short of stating when not to use it or naming the search/compare tools as alternatives.

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