Skip to main content
Glama
qune-tech

qune-tech/ocds-mcp

list_releases

List and filter German public procurement releases by criteria like month, CPV code, category, method, value range, and buyer name. Supports pagination for tender discovery.

Instructions

List and filter OCDS procurement releases by structured criteria: month, CPV code prefix, procurement category, procurement method, value range, and buyer name. Supports pagination. Data is fetched from the REST API. Use this for tender discovery before drilling into specific releases with get_release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyer_nameNoFilter by buyer name (case-insensitive substring match)
cpv_prefixNoFilter by CPV code prefix (e.g. '45' for construction, '72' for IT)
deadline_afterNoOnly include tenders with deadline on or after this ISO-8601 datetime
deadline_beforeNoOnly include tenders with deadline on or before this ISO-8601 datetime
eu_fundedNoFilter by EU funding status (true = EU funded)
has_awardsNoFilter by whether the release has awards with suppliers (true/false)
limitNoMaximum number of results (default 20, max 200)
location_nutsNoFilter by delivery location NUTS code prefix (e.g. 'DE3' for Berlin)
main_procurement_categoryNoFilter by main procurement category (e.g. 'works', 'goods', 'services')
monthNoFilter by month in YYYY-MM format
nuts_codeNoFilter by NUTS code prefix (e.g. 'DE2' for Baden-Württemberg)
offsetNoOffset for pagination (default 0)
procurement_methodNoFilter by procurement method (e.g. 'open', 'selective', 'limited')
result_codeNoFilter by result code (e.g. 'selec-w' for selected winner, 'clos-nw' for closed no winner)
statusNoFilter by tender status (e.g. 'active', 'complete', 'cancelled')
submission_deadline_afterNoOnly include tenders with submission deadline on or after this ISO-8601 datetime
submission_deadline_beforeNoOnly include tenders with submission deadline on or before this ISO-8601 datetime
tagNoFilter by lifecycle tag (e.g. 'tender', 'award', 'planning')
value_maxNoMaximum tender value
value_minNoMinimum tender value
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions pagination and data source ('fetched from the REST API') but fails to discuss response format, defaults, error handling, rate limits, or whether the operation is read-only. Given the 20-parameter complexity, this is insufficient for an agent to safely invoke the tool.

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 three concise sentences, each carrying essential information: purpose and filters, pagination and data source, and usage guidance. No fluff or repetition.

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

Completeness2/5

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

With 20 parameters, no output schema, and no annotations, the description is too sparse. It does not clarify how filters combine (AND/OR), default sorting or ordering, response structure, or error behavior. The agent would lack critical context for correct invocation.

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%, meaning every parameter has a description in the input schema. The tool description only summarizes a subset of filters without adding new meaning, so the baseline score of 3 is appropriate.

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 verb 'List and filter' and the resource 'OCDS procurement releases', specifies several filtering criteria (month, CPV prefix, etc.), and explicitly distinguishes from the sibling tool `get_release` by stating it is for 'tender discovery before drilling into specific releases'.

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

Usage Guidelines4/5

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

The description provides explicit guidance: 'Use this for tender discovery before drilling into specific releases with get_release.' This clarifies the primary use case and indicates an alternative tool for detailed information, though it does not list when NOT to use it or mention any prerequisites.

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/qune-tech/vergabe-mcp'

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