Aurelmark

List TED tender deadline changes

tenders_list_deadline_changes

Read-onlyIdempotent

Returns submission-deadline changes for one watched TED tender, from its official TED notices: each event per lot with old and new deadline (local and UTC), plus the current deadlines. Use it after tenders_list_watched gave you a notice_id; use funding_list_changes for grant calls and compliance_list_deadlines for legal dates. Inputs: notice_id (required, TED publication number, e.g. 662865-2026), limit (1 to 50, default 50) and cursor (next_cursor to page or checkpoint_cursor to poll later; cursors belong to that notice and expire after 24 hours). Output: events[] with lot, old and new deadlines and the TED notice link, current deadlines, cursors and freshness (checked hourly). A notice we do not watch returns notice_not_tracked. 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": "tenders_list_deadline_changes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Changes per page, 1 to 50 (default 50); e.g. 20.
`cursor`	No	Opaque signed base64url next_cursor or checkpoint_cursor for this same notice, 20 to 400 ASCII letters/digits/_/-. Copy unchanged; refresh within 24 hours; omit on first call. Example illustrates syntax only, not a valid signature.
`notice_id`	Yes	TED publication number of the watched tender, e.g. 662865-2026

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds genuinely new behavior: the notice_not_tracked error for unwatched notices, cursor expiry at 24 hours, hourly freshness checks, and the free/metered quota rules including sample truncation. The quota paragraph is accurate but generic boilerplate shared across routes, which keeps it from a 5.

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 first three sentences are tightly front-loaded and well ordered (purpose, routing, inputs, output, error). The trailing terms block on free answers, metered routes, sanctions edge cases and API keys is long and only loosely tied to this specific tool, diluting the signal.

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?

There is no output schema, and the description compensates by naming the return shape (events[] with lot, old/new deadlines in local and UTC, TED notice link, current deadlines, cursors, freshness) plus the failure code. For a read-only three-parameter list tool this is close to complete; only per-event ordering or payload size expectations are left unstated.

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 notice_id, limit and cursor are already fully documented in the schema, including the next_cursor/checkpoint_cursor distinction and the 24-hour refresh. The description restates default 50 and the cursor expiry without adding new syntax or edge-case meaning, so it sits at the baseline for a fully documented 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?

States a specific verb and resource ('Returns submission-deadline changes for one watched TED tender') and immediately scopes it to official TED notices. It explicitly names the siblings it is not (funding_list_changes, compliance_list_deadlines) and the sibling that feeds it (tenders_list_watched), so an agent can distinguish it without opening any schema.

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?

Gives an explicit sequencing rule ('after tenders_list_watched gave you a notice_id') and routes two adjacent use cases to named alternatives. The when-to-use condition is concrete rather than implied.

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

All Aurelmark tools Inspect

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.