Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Newest EU public procurement notices from TED in one call: notice number, publication date, buyer, notice type, title, l

eu_tenders
Read-onlyIdempotent

Newest EU public procurement notices from TED in one call: notice number, publication date, buyer, notice type, title, link to the notice (days=1..14, country=3-letter code such as DEU or FRA, count up to 50). One poll replaces watching TED. Pay per call $0.002 USDC on Base via x402.

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": "eu_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo1 to 14
countNoup to 50
countryNo3-letter code, e.g. DEU
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile. The description adds genuinely new behavioral context: this is a paid endpoint at $0.002 USDC on Base via x402, which an agent must know before calling. It stops short of describing rate limits, pagination, or empty-result behavior.

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?

The purpose and returned fields are front-loaded in a single dense sentence, followed by the value proposition and pricing. Every clause carries information; the parenthetical is slightly crowded but not wasteful.

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 compensates by listing the exact fields returned, and it covers the payment handshake that would otherwise surprise an agent. Missing only default values and behavior when zero notices match, which are minor gaps for a simple fetch 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 description coverage is 100%, so all four parameters are already documented in structured form. The description's parenthetical (days=1..14, country=3-letter code such as DEU or FRA, count up to 50) restates the schema almost verbatim and adds no new semantics, so the baseline 3 applies.

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 names a specific retrieval verb and resource ('Newest EU public procurement notices from TED') and enumerates the returned fields (notice number, publication date, buyer, notice type, title, link). No sibling tool covers this domain, and the scope is unmistakable.

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?

'One poll replaces watching TED' implies when to reach for it, but there is no explicit when-not guidance, no stated defaults for days/count, and no named alternative. Usage is inferable rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources