Skip to main content
Glama

Ted Eu

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Notice

get_notice
Read-onlyIdempotent

Fetch a single TED notice by publication number (e.g. "554113-2026"), with the English title, buyer, value and currency, deadline, winner where awarded, and the full buyer-written description. Accepts notice_id / id as aliases.

Input Schema

NameRequiredDescriptionDefault
idNoAlias for publication_number.
notice_idNoAlias for publication_number.
publication_numberYesTED publication number, format "<num>-<year>". notice_id and id are accepted as aliases.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "publication_number": "123456-2025"
-  }
-]New value: +[
+  {
+    "publication_number": "554113-2026"
+  }
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alias for publication_number.",
+  "type": "string"
+}
    • addedInput schema / properties / notice_id
      Added value: +{
+  "description": "Alias for publication_number.",
+  "type": "string"
+}
    • changedInput schema / properties / publication_number / description
      Previous value: -"TED publication number, format \"<num>-<year>\""New value: +"TED publication number, format \"<num>-<year>\". notice_id and id are accepted as aliases."
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "publication_number": "123456-2025"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "A complete TED notice object with all details",
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about the fields returned (title, buyer, value, currency, deadline, winner 'where awarded', full description) and the alias behavior, which goes beyond the annotations without contradicting them.

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?

The description is a single, information-dense sentence that front-loads the core action ('Fetch a single TED notice by publication number') and then lists the returned fields and aliases. Every clause earns its place; no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-fetch tool, the description is complete. Combined with the output schema (which explains return values) and annotations (which cover safety), the description provides enough context for an agent to select and invoke the tool correctly, including the exact format of the identifier and aliases.

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 three parameters, including aliases. The description adds an example format and reiterates aliases, but this is marginal given the schema is already thorough.

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 uses a specific verb ('Fetch') and resource ('a single TED notice') with the identification method ('by publication number'). It clearly differentiates from sibling tools like search_notices by focusing on fetching a specific notice by ID rather than searching.

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?

The description clearly implies the tool is for fetching a known notice by publication number, which is distinct from searching (search_notices). However, it does not explicitly state when not to use it or mention alternatives by name, only that it accepts aliases for the ID.

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

All Ted Eu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources