Skip to main content
Glama
Sign In
qune-tech/ocds-mcp

qune-tech/ocds-mcp

by qune-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

get_release

Fetch the complete OCDS release data for a tender using its OCID. Includes tender details, buyer, parties, awards, and lot structure.

Instructions

Get the full OCDS release data for a specific tender by its OCID (Open Contracting ID). Returns the complete release JSON including tender details, buyer, parties, awards, and lot structure. Data is fetched from the REST API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ocid": "<ocid>"
    },
    "name": "get_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocidYesThe OCID (Open Contracting ID) of the release to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It mentions the output includes specific fields and that data comes from a REST API, but lacks details on error handling, authentication, or rate limits.

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?

The description is concise with two sentences. The first clearly states the purpose, and the second adds useful output details. No extraneous information.

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?

Given no output schema, the description adequately explains the return value (complete release JSON with key fields). It could mention error cases, but overall it provides sufficient context for a simple retrieval tool.

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 coverage is 100% for the single parameter 'ocid', and its schema description adequately explains it. The tool description adds no extra semantic value beyond the schema.

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 the tool's purpose: retrieving the full OCDS release data for a specific tender by OCID. It distinguishes from sibling tools like list_releases, which likely returns multiple records.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify that users need an OCID, or contrast it with list_releases for broader queries.

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