Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver el expediente OCDS de un contrato SERCOP

get_contrato_info
Read-only

Fetch a full OCDS record for a SERCOP procurement process by OCID, covering buyer, tender, awards, and contracts.

Instructions

Full OCDS record of one SERCOP procurement process (ocid from search_contratos): buyer, tender, awards, contracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ocidYesOpen Contracting ID, e.g. "ocds-5wno2w-001-LICO-GPLR-2020-2805"
formatNotext summary (default) or json structured result.text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / ocid / description
      Added value: +"Open Contracting ID, e.g. \"ocds-5wno2w-001-LICO-GPLR-2020-2805\""
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / ocid / title
      Removed value: -"Ocid"
    • removedInput schema / title
      Removed value: -"get_contrato_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_contrato_infoDictOutput"
  4. First observedv0.8.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds that this returns the *full* record and names the four OCDS blocks, but says nothing about record size, potential latency, or error behavior on an unknown ocid.

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?

A single dense sentence, front-loaded with the resource and scope, with every clause carrying information (scope, id provenance, returned sections). No filler.

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

Completeness4/5

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

With no output schema, the description correctly compensates by naming the returned OCDS sections, and annotations carry the safety profile. Only gap is the absence of any note about response size or failure modes for a bad ocid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both ocid (including a concrete example value) and the format enum documented in-schema, so the baseline is 3. The description only adds that ocid originates from search_contratos, marginal value beyond the schema.

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?

States a specific verb+resource: retrieving the full OCDS record for one SERCOP procurement process, and enumerates the sections returned (buyer, tender, awards, contracts). The parenthetical tying the ocid to search_contratos distinguishes it from the search sibling, though it doesn't explicitly frame itself as the 'detail view' counterpart.

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

Usage Guidelines3/5

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

The phrase '(ocid from search_contratos)' implies the required upstream workflow — search first, then fetch detail. There is no explicit when-not guidance, no note about what to do if the ocid is unknown or invalid, and no named exclusion of alternatives.

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

Deploy Server

Other Tools