Skip to main content
Glama
Sign In

Aurelmark

by io.github.Ishan73744
OverviewDiscussionsAdmin

Get one EU contract award

awards_get_contract
Read-onlyIdempotent

Returns one EU contract award notice from official TED by its publication number: winners, buyer, value, CPV, dates, lots, notice URL and SHA-256 proof. Use it when you already have a notice_id; use awards_list_contracts to discover awards or filter by company, CPV or country. Input: notice_id (required, TED publication number, 1 to 8 digits, hyphen, year, e.g. 718666-2026). Output: award and feed (coverage, checked_at). A notice we have not stored returns award_not_found; awards_feed_not_ready means the feed is not loaded yet. Reads stored observations (about 45 days), not a live TED lookup. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

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": {
      "notice_id": "<notice_id>"
    },
    "name": "awards_get_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesTED publication number, e.g. 718666-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that results come from stored observations (~45 days) rather than a live TED lookup, naming the specific error states (award_not_found, awards_feed_not_ready), and spelling out metering, free-answer limits, and sample truncation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is front-loaded and well organized with Input/Output/Terms labels, but the final third is a dense block of pricing, metering, sanctions-search edge cases, and free-tier policy that is disproportionate to a single-lookup read tool. Several of those sentences do not earn their place in a tool description.

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 one-parameter read tool with no output schema, the description still specifies the return shape (award and feed with coverage/checked_at), the two failure modes, and the data-freshness caveat. An agent has everything needed to call it and interpret both success and failure.

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% and the schema already carries the regex pattern and an example, so the description's "TED publication number, 1 to 8 digits, hyphen, year, e.g. 718666-2026" largely restates structured data. The label of what the ID represents is mildly useful but adds little beyond the schema.

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?

"Returns one EU contract award notice from official TED by its publication number" names a specific verb, resource, source, and lookup key, and immediately enumerates the returned fields (winners, buyer, value, CPV, dates, lots, notice URL, SHA-256 proof). It is unambiguously distinguishable from awards_list_contracts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the selection condition explicitly: "Use it when you already have a notice_id; use awards_list_contracts to discover awards or filter by company, CPV or country." Both the when and the named alternative with its own conditions are present.

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

All Aurelmark 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