Skip to main content
Glama

BRAINIAC Procurement Intelligence

Resolve EU notice

procurement-intelligence_eu-notices-resolve
Read-onlyIdempotent

Retrieve full details of an EU procurement notice from TED by notice ID. Price $0.05 USDC. POST /api/v1/procurement-intelligence/eu/notices/resolve. An unpaid call returns the x402 payment terms and does not run.

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": {
      "noticeId": "<noticeId>"
    },
    "name": "procurement-intelligence_eu-notices-resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
noticeIdYesnoticeId, string. Required.

Output Schema

NameRequiredDescriptionDefault
inputNoinput. Object.
noticeNonotice. Null.
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 cover safety (readOnly, idempotent, non-destructive, open-world), so the description earns credit for adding what annotations cannot: a $0.05 USDC price, the underlying POST endpoint, and the x402 paywall behavior where an unpaid call returns payment terms instead of results. It stops short of describing response shape, but an output schema exists to carry that.

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 tight sentences, front-loaded with the purpose and followed by cost and payment behavior. The raw endpoint path is arguably the least useful element for an agent, but it is cheap and unambiguous.

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?

For a one-parameter lookup with a rich annotation set and an output schema, the description supplies the missing pieces: cost, transport, and paywall semantics. Only the return-value characteristics are left unaddressed, which the output schema covers.

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% for the single noticeId parameter, so the schema already documents it fully. The description only restates that lookup is 'by notice ID' without adding format, sourcing, or validation detail, which is the expected baseline.

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 states a specific verb and resource: retrieve full details of an EU procurement notice from TED, keyed by notice ID. That distinguishes it from the sibling search tool by input mode (ID lookup vs query), though it never names the search sibling for contrast.

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 only implied: the agent must already hold a notice ID, so the resolve path is the right one. There is no explicit when-to-use guidance, no statement about where to obtain a notice ID, and no named alternative for discovery-style queries.

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