Skip to main content
Glama

TORDO — Mercado Público de Chile

Precio de referencia de un producto

precio_de_producto

Bandas de precio históricas de un producto (código ONU): percentiles 10 a 90, con el nivel de datos usado, la confianza y el tamaño de muestra. Si se indica organismo, usa sus datos y sólo cae al sector o al país cuando no tiene suficientes.

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_producto": "<codigo_producto>"
    },
    "name": "precio_de_producto"
  }
}

Input Schema

NameRequiredDescriptionDefault
organismo_idNo
codigo_productoYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / codigo_producto / maxLength
      Added value: +64
    • addedInput schema / properties / codigo_producto / minLength
      Added value: +1
    • changedInput schema / properties / organismo_id / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 64,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the fallback hierarchy (organismo → sector → país) and notes that data level, confidence and sample size accompany the result, which is genuinely useful behavioral context. It does not state whether the response signals which fallback level was used, nor any auth or rate-limit traits, leaving notable gaps.

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?

Two sentences, no filler: what the tool returns and how the organismo filter behaves. Both facts are front-loaded and every clause earns its place.

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-shape explanation is not required, and both parameters are addressed. The remaining gap is the missing routing guidance relative to sibling tools for an agent choosing among them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate: it clarifies that codigo_producto is an ONU code and explains the conditional behavior and fallback of organismo_id. That covers both parameters well, though it never states that organismo_id is optional or what an omitted value defaults to.

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 resource ('bandas de precio históricas de un producto') keyed by ONU code, which is clearly distinguishable from siblings like buscar_productos or perfil_de_comprador. It stops short of explicitly naming an alternative, but the verb+resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives a concrete conditional rule — if organismo_id is supplied, use its data, falling back to sector or country when the sample is insufficient — which is real usage guidance for that parameter. However, there is no explicit statement of when to use this tool versus buscar_productos or panel_de_licitacion.

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