Retrieve the SECOP II and Colombia Compra Eficiente taxonomy map, including six domains and eleven main links, to navigate procurement data and optionally filter by category code.
Devuelve el mapa taxonómico de 6 dominios y 11 enlaces principales de SECOP II y Colombia Compra Eficiente.
| Name | Required | Description | Default |
|---|---|---|---|
| category_code | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden and discloses almost nothing: it does not say whether this is a pure read of static reference data, whether results are cached, or whether any side effects occur. Only the output schema hints at the return shape.
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?
A single efficient sentence with the resource front-loaded and no filler. It is concise, though brevity costs it the parameter and usage detail it needed.
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?
The output schema exists, so return values need not be explained. However, the meaning of the sole optional parameter and the intended usage context are both missing, which leaves real gaps for an agent deciding whether to filter.
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 0% and the description never mentions 'category_code', so an agent cannot tell what the optional filter does or what values it accepts (no enum). With one undocumented parameter, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Devuelve') and resource ('mapa taxonómico') and even quantifies scope (6 dominios, 11 enlaces). It is clearly distinct from search/crawl siblings, though it never names those alternatives explicitly.
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?
No guidance on when to call this versus the other SECOP tools, and no mention of prerequisites or typical workflow position. The only implicit cue is that this is reference/discovery data rather than a search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.