Skip to main content
Glama

TORDO — Mercado Público de Chile

Panel de una licitación

panel_de_licitacion

Todo lo que hace falta para decidir si postular a una licitación, en una sola llamada: perfil del comprador, si la ventana de preparación es holgada o apretada, los competidores habituales, y las bandas de precio de sus productos con su confianza. Úsala en vez de encadenar varias herramientas.

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": {
      "codigo": "<codigo>"
    },
    "name": "panel_de_licitacion"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / codigo / maxLength
      Added value: +64
    • addedInput schema / properties / codigo / minLength
      Added value: +1
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a heavy aggregate call returning derived judgements ('si la ventana de preparación es holgada o apretada') and confidence-tagged price bands, which is genuine behavioral value, but it says nothing about read-only nature, cost/latency of the aggregation, data freshness, or permissions.

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?

A single front-loaded sentence with the purpose first, then a colon-delimited inventory of what is returned, then the usage directive. Dense but well ordered; it could be split for readability but wastes no words.

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 return values need not be re-explained, and complexity is low (one parameter). Purpose and usage are complete; the only real omission is any description of the 'codigo' input, which is handled (poorly) under parameter semantics rather than here.

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% for the single parameter 'codigo' (1-64 chars). The description never mentions the input at all — no format, no example, no note on whether it is a tender ID or a product code — leaving the only required argument undocumented in both schema and prose.

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 precisely what the tool returns (buyer profile, preparation-window slack, usual competitors, price bands with confidence) and frames it as a one-call aggregate. The enumerated contents map directly onto the sibling tools (perfil_de_comprador, precio_de_producto), so an agent can tell it apart from them without opening any 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 en vez de encadenar varias herramientas' gives an explicit usage instruction and a preferred alternative to manual chaining. It lacks any when-not guidance (e.g., when a single cheap sibling call is enough), but the selection context is clear.

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.