Skip to main content
Glama

eu_tenders

Search public tenders across France’s BOAMP and the EU’s TED by keyword and date; get merged, sorted results with buyer, deadline, country, CPV codes, and links.

Instructions

Public tender scanner: keyword search across BOAMP (France) and TED (EU Official Journal, all member states) since a date, merged and sorted: title, buyer, publication date, deadline, notice type, country, CPV codes and link. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "q": "<q>"
    },
    "name": "eu_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeywords
maxNo1-50 per source
sinceNoYYYY-MM-DD, default 30 days ago
countryNoTED buyer country ISO alpha-3, e.g. DEU
sourcesNoboamp,ted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the paid model, the exact price and chain, the x402 protocol, and the concrete failure mode (402 challenge) when unauthenticated. It stops short of covering rate limits, result caps per source, or behavior on empty results, but the payment/auth disclosure is the highest-value trait an agent needs here.

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?

Two sentences, both front-loaded: capability and sources first, cost and failure mode second. The field enumeration earns its space because no output schema exists, and there is no filler wording.

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?

Because there is no output schema, the enumerated return fields (title, buyer, publication date, deadline, notice type, country, CPV codes, link) are necessary and present. The payment and auth behavior is fully explained; only secondary details such as pagination behavior beyond the per-source cap and error handling are left implicit.

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 the schema already documents all five parameters including defaults and range. The description adds only marginal semantics beyond that — clarifying that TED means the EU Official Journal across all member states, and that results are merged and sorted — so the baseline 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?

States a specific verb and resource ("keyword search" over public tenders) and names the two concrete data sources, BOAMP and TED, with scope ("since a date, merged and sorted"). It then enumerates the returned fields, so an agent knows exactly what class of result to expect without opening a schema.

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?

Gives the operative precondition for calling it at all — it costs 0.003 USDC on Base per successful call and returns a 402 challenge without a payment key — which is the decisive gating context for an agent. It does not, however, state when to prefer or avoid this tool relative to other lookups, though no sibling in the list covers tender search.

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