obtener_enlace_documentoEntrega la ficha pública del proceso y la lista de sus adjuntos. Para leer uno, usa descargar_y_leer_documento.
Entrega la ficha pública del proceso y la lista de sus adjuntos. Para leer uno, usa descargar_y_leer_documento.
| Name | Required | Description | Default |
|---|---|---|---|
| id_documento | No | ID del adjunto, si ya lo tienes (opcional). | |
| codigo_compra | Yes | Código de la Compra Ágil (Ej: "2494-141-COT26"). |
Changes observed during successful MCP inspections.
v2.9.3Input schema / properties / codigo_compra / descriptionPrevious value: -"Código de la Compra Ágil asociada (Ej: \"2494-141-COT26\"). Requerido para generar el enlace de la ficha pública."New value: +"Código de la Compra Ágil (Ej: \"2494-141-COT26\")."Input schema / properties / id_documento / descriptionPrevious value: -"ID único del documento. Ej: \"123456\" o un UUID como \"5f47e991-c525-40a0-b36c-44d53e538ae5\"."New value: +"ID del adjunto, si ya lo tienes (opcional)."Input schema / requiredPrevious value: -[
- "id_documento",
- "codigo_compra"
-]New value: +[
+ "codigo_compra"
+]v2.7.0Input schema / properties / codigo_compraAdded value: +{
+ "description": "Código de la Compra Ágil asociada (Ej: \"2494-141-COT26\"). Requerido para generar el enlace de la ficha pública.",
+ "type": "string"
+}Input schema / properties / id_documento / descriptionPrevious value: -"ID único del documento. Ej: \"123456\" de la lista de documentos de una compra."New value: +"ID único del documento. Ej: \"123456\" o un UUID como \"5f47e991-c525-40a0-b36c-44d53e538ae5\"."Input schema / requiredPrevious value: -[
- "id_documento"
-]New value: +[
+ "id_documento",
+ "codigo_compra"
+]v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world access are covered. The description adds that the return is a 'ficha pública' plus attachment list, but says nothing about rate limits, authentication, or response format beyond that, which is adequate given the annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no waste; the primary function is front-loaded and the routing hint follows immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only retrieval tool with fully documented parameters and no output schema, the description tells the agent what it returns and where to go for the follow-up action. Only the link/URL aspect implied by the name goes unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, documenting both codigo_compra (with format example) and the optional id_documento, so the schema carries the parameter burden. The description adds no meaning beyond the schema, which is the expected baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource: it delivers the process's public record plus its attachment list, and it names the sibling descargar_y_leer_documento for the read case. The one weakness is that the tool name emphasizes 'enlace' (a link/URL) while the description never mentions returning links, creating minor ambiguity about the exact output.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit alternative for the adjacent operation: 'Para leer uno, usa descargar_y_leer_documento', routing the agent away from this tool when actual reading is wanted. It lacks when-not conditions or prerequisites, but the single most important branch point is covered.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.