Skip to main content
Glama

TORDO — Mercado Público de Chile

Perfil de un comprador

perfil_de_comprador

Cómo se comporta un organismo público: qué tan transparente es su historial, cuánto de lo que llama termina adjudicando y sus señales de riesgo. Sirve para decidir si conviene trabajar con él antes de mirar el precio.

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": {
      "organismo_id": "<organismo_id>"
    },
    "name": "perfil_de_comprador"
  }
}

Input Schema

NameRequiredDescriptionDefault
organismo_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/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 does disclose the substance of what the profile contains (transparency level, award ratio, risk signals), which is useful behavioral context, but says nothing about read-only safety, permissions, or data freshness, and the return shape is left entirely to the output schema.

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 what the profile measures and then why it matters. Efficient, with little wasted text, though "qué tan transparente es su historial" is somewhat abstract phrasing.

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?

Because an output schema exists, the description need not describe return values, and it adequately explains the purpose. The remaining gap is the undocumented required input parameter and the absence of any indication of how to source organismo_id.

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?

There is one required parameter (organismo_id) with 0% schema description coverage, and the description never mentions it. It does not explain the expected identifier format, length constraints, or where the agent should obtain a valid value, so the description fails to compensate for the schema gap.

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 clearly what the tool returns: a behavioral profile of a public buyer organism covering transparency of its history, how much of what it tenders ends up being awarded, and risk signals. It is specific about the resource (comprador/organismo) but never uses an explicit action verb and does not name or contrast with the sibling tools, so sibling differentiation is left to inference.

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?

"Sirve para decidir si conviene trabajar con él antes de mirar el precio" gives a concrete decision context and implicitly positions it against precio_de_producto. No explicit exclusions or alternative tools are named, but the when-to-use condition 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.