Skip to main content
Glama
Sign In
open-data-mcp

open-data-mcp

by markatdataandbeyond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dataandbeyond--eu-tenders

Read-only

Search and monitor EU public procurement notices from TED, including buyer, deadline, value, and winners, using the official API v3.

Instructions

EU public procurement notices from TED: buyer, deadline, value and winners. Calls the official TED API v3 directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataandbeyond--eu-tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvCodesNoe.g. 72000000 (IT services). Example values: ["72000000"]
keywordsNoFull-text search, e.g. cloud software. Example values: "software"
languageNo3-letter code: eng, dan, swe, deu, fra... Example values: "eng"eng
rawQueryNoOverrides all filters.
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
countriesNoISO-2 or ISO-3 codes, e.g. DK, SE, NO, FI. Example values: ["DE"]
maxResultsNoNewest first. Example values: 20
onlyOpenCallsNoContract notices / calls for competition only.
publishedFromNoOptional start date.
publishedWithinDaysNoIgnored if publishedFrom is set. Example values: 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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. The description adds one useful piece of context beyond that — it hits the official TED API v3 directly, implying live external data — but says nothing about the asynchronous Actor-run/polling behavior that the waitSecs parameter implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with zero padding, and the resource identity is front-loaded. It is efficient but arguably too sparse for a 10-parameter tool with no output schema.

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

Completeness3/5

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

The description covers what the tool returns and its data source, and the annotations plus full schema coverage handle safety and parameters. However, for a 10-parameter open-world search tool with no output schema, it omits result-shape expectations, pagination/ordering semantics (maxResults is 'newest first' only in the schema), and the async run model.

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%, so every parameter is already documented in the schema, including the rawQuery override and waitSecs polling semantics. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

Names the specific resource (EU public procurement notices from TED) and enumerates the returned fields (buyer, deadline, value, winners), which tells an agent exactly what it gets. It lacks an explicit verb (search vs. monitor vs. list) and does not name any sibling, though the domain is unmistakably distinct from the other dataandbeyond tools.

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?

The description gives no when-to-use/when-not guidance, no mention of the rawQuery override that supersedes all filters, and no indication of typical query shapes. An agent must infer usage entirely from the schema field names.

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