Skip to main content
Glama

Indicadores Argentina

by ar.indicadores
OverviewDiscussionsAdmin

Detalle de un llamado

ficha_llamado
Read-only

Detalle de un proceso de contratación del Estado argentino a partir del slug de un resultado de buscar_llamados: cronograma (retiro del pliego, consultas, presentación y apertura de ofertas), link y plataforma para participar, presupuesto oficial, valor del pliego y garantías cuando el aviso los publica, desenlace y el historial de publicaciones (el llamado y cada circular o prórroga). Con parecidas=true suma lo que el Estado ya adjudicó por algo parecido en los cinco años anteriores (organismo, empresa ganadora, fecha, monto y monto en pesos de hoy, con extremos y cuartiles): es el monto del contrato entero, no un precio unitario. Cuesta 1 crédito, más 1 por las parecidas si vuelven con alguna; un slug que no existe no se cobra.

Input Schema

NameRequiredDescriptionDefault
slugYesslug de un resultado de buscar_llamados
parecidasNotrue para sumar las adjudicaciones parecidas (+1 crédito si hay alguna)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / parecidas
      Added value: +{
+  "description": "true para sumar las adjudicaciones parecidas (+1 crédito si hay alguna)",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), and the description adds non-obvious behavior that annotations cannot: cost of 1 credit, +1 for parecidas only if results come back, and that a nonexistent slug is not charged. It also enumerates what is returned, including conditional fields ('cuando el aviso los publica').

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?

Front-loaded with purpose, then parecidas semantics, then cost; the ordering is logical and each sentence carries real information. It is a dense, long single paragraph, which makes scanning harder than a short bulleted structure would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing return values, and it does so thoroughly (cronograma items, participation link/platform, presupuesto, pliego, garantías, desenlace, historial de publicaciones y circulares). Combined with cost and edge-case billing behavior, an agent has everything needed to call it correctly.

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 coverage is 100%, so baseline is 3; the description goes beyond by spelling out exactly what parecidas adds (organismo, empresa ganadora, fecha, monto, monto en pesos de hoy, extremos y cuartiles) and warning that it is the whole-contract amount, not a unit price — a meaning the schema does not convey. Slug handling is not elaborated beyond the schema line.

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?

Names a specific resource (detalle de un proceso de contratación) and its precise input source: the slug from a buscar_llamados result. This immediately distinguishes it from buscar_llamados (search) and from ficha_empresa/ficha_persona (other detail tools for different entities).

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?

Explicitly states the prerequisite that the slug must come from buscar_llamados, and gives the condition for parecidas=true (want comparable past awards). It does not name an alternative tool or a when-not-to-use case, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Indicadores Argentina toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources