Skip to main content
Glama
juandavidsernav

secop-mcp-server

resumen_contratacion

Get a condensed view of Colombian public contracts with key fields to quickly explore results before requesting full details.

Instructions

Resumen condensado de contratos con solo los campos clave.

Retorna una vista simplificada con: entidad, proveedor, objeto (truncado), valor, estado y fecha. Ideal para explorar resultados antes de pedir el detalle completo con buscar_contratos_secop2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entidadNo
proveedorNo
nit_proveedorNo
departamentoNo
objetoNo
fecha_desdeNo
fecha_hastaNo
limiteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses a simplified view with truncated object, but does not explain search behavior, pagination, or if parameters are exact/fuzzy matches.

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, front-loaded with purpose, no fluff. Every sentence adds value.

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?

Provides overview purpose and output structure, but lacks guidance on parameter usage (dates, matching) despite 8 parameters with 0% schema coverage. Adequate for a summary tool but incomplete for effective invocation.

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%, yet the description does not explain input parameters. It lists output fields but not input semantics, failing to compensate for the lack of schema descriptions.

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?

The description clearly states it provides a condensed summary of contracts with key fields, and explicitly differentiates from sibling 'buscar_contratos_secop2' which gives full detail.

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

Usage Guidelines5/5

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

The description explicitly says 'Ideal para explorar resultados antes de pedir el detalle completo con buscar_contratos_secop2', providing clear usage context and a direct alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juandavidsernav/secop-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server