Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

search_eu_ted_public_tenders

Read-onlyIdempotent

Search EU TED public procurement notices, contract awards, CPV codes, contracting authorities, and tender documents by keyword and country to identify relevant government opportunities.

Instructions

Search European Union Tenders Electronic Daily (TED) public procurement notices, government contract awards, CPV industry classifications, contracting authorities, and official tender documents.

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": {
      "query": "<query>"
    },
    "name": "search_eu_ted_public_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProcurement keyword, sector, or CPV description (e.g., "cloud infrastructure", "cybersecurity").software
countriesNoISO country codes to filter (e.g., ["DEU", "FRA", "NLD", "ESP"]).
maxResultsNoMaximum number of EU tender notices to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and repeatability profile is covered without description help. The description adds only the breadth of searched content; it says nothing about rate limits, authentication, pagination, result freshness, or whether the open-world search may return zero hits for narrow country filters.

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?

A single sentence with the action and resource front-loaded, followed by a compact enumeration of covered content. It is efficient, though the trailing list is somewhat long and could be trimmed without loss.

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 100% schema coverage, full annotations, and no output schema, the description's job is mostly to establish scope and subject matter, which it does by naming the notice types returned. The main residual gap is that nothing is said about result ordering, pagination, or total-count behavior for a capped search.

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% and each of the three parameters already carries an example-bearing description, so the baseline of 3 applies. The tool description adds no additional meaning about how query interacts with countries or how maxResults affects response shape.

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?

The description gives a specific verb (Search) plus a precisely named resource (European Union Tenders Electronic Daily / TED public procurement notices) and enumerates the content types covered: contract awards, CPV classifications, contracting authorities, tender documents. It is clearly distinguishable from domain-distant siblings like search_fda_and_product_safety_compliance or search_sec_edgar_filings by jurisdiction and subject matter, though it never explicitly contrasts itself with them.

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?

Usage is implied by the enumerated content types - an agent can infer this is the tool for EU procurement lookups - but there is no explicit statement of when to use it, when not to, or which sibling to prefer for adjacent needs such as sanctions screening or company enrichment. No prerequisites or exclusions are given.

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