Skip to main content
Glama

BRAINIAC Procurement Intelligence

Search EU notices

procurement-intelligence_eu-notices-search
Read-onlyIdempotent

Search published EU procurement notices from TED with filtering by keyword, CPV code, NUTS code, and date range. Price $0.05 USDC. POST /api/v1/procurement-intelligence/eu/notices/search. An unpaid call returns the x402 payment terms and does not run.

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": "procurement-intelligence_eu-notices-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
cpvCodeNocpvCode, string. Optional.
endDateNoendDate, string. Optional.
keywordNokeyword, string. Optional.
nutsCodeNonutsCode, string. Optional.
startDateNostartDate, string. Optional.

Output Schema

NameRequiredDescriptionDefault
inputNoinput. Object.
totalNototal. Number.
noticesNonotices. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.05 USDC cost and the fact that an unpaid call returns x402 payment terms without executing, which is critical for an agent to plan around. It stops short of covering result ordering or rate limits.

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?

Three short sentences, front-loaded with the purpose, followed by cost/endpoint and the payment-gating caveat. The literal endpoint path is marginally redundant for an MCP caller, but overall there is no filler.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description covers purpose, filters, cost and payment gating, leaving only minor gaps such as default result ordering and how limit interacts with result sets.

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 coverage is 100%, so every parameter is already documented in the schema, which sets the baseline at 3. The description restates the filter names but adds no format detail (e.g., expected date string format or CPV code structure) beyond what the schema provides.

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 uses a specific verb ('Search') with a precise resource ('published EU procurement notices from TED') and enumerates the filter dimensions (keyword, CPV, NUTS, date range). This makes the tool distinguishable from siblings like us-awards-search or eu-notices-resolve by domain and intent, though it never explicitly names an alternative.

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 filter list and the domain ('EU notices from TED'), and the payment caveat tells the agent a call may not execute without payment. However, there is no explicit guidance on when to choose this over procurement-intelligence_search or eu-notices-resolve, and no stated prerequisites for obtaining payment.

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