Aurelmark

List watched TED tenders

tenders_list_watched

Read-onlyIdempotent

Returns the official TED (Tenders Electronic Daily) tenders we monitor for submission-deadline changes, with each one's notice_id, last check time and freshness. Use it first to find a notice_id for tenders_list_deadline_changes; use awards_list_contracts for contract winners. No inputs. It does not add a watch (ask hello@aurelmark.live). Output: the watched notices with their notice_id values, last check times and freshness, as /v1/coverage reports them (checked hourly). Always free and unlimited, no key needed. 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

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": "tenders_list_watched"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.3/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, and the description adds genuinely new behavior: an hourly check cadence, a 'freshness' notion, and the fact that adding a watch is out of scope. The remaining billing text is largely generic template boilerplate rather than behavior specific to this tool, and the 'always free and unlimited' line sitting beside a long metered-route quota paragraph mildly muddies the cost picture.

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

Conciseness2/5

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

The purpose and routing information is correctly front-loaded in the first two sentences, but roughly two thirds of the text is reusable licensing/quota boilerplate about metered HTTP routes and free-answer samples that is not specific to a zero-input listing tool. For a no-parameter read, this is significant bloat that dilutes the actionable 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?

For a zero-param, read-only listing with no output schema, the description names the returned fields (notice_id, last check time, freshness), the update cadence (hourly), and the downstream tool that consumes notice_id. Nothing needed to call it correctly is missing; the only shortfall is that the pricing paragraph adds length rather than completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, so parameter semantics are trivially satisfied; the description confirms this with 'No inputs.' There is nothing further a schema could not already say, and nothing is left ambiguous.

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 the official TED tenders we monitor for submission-deadline changes') and enumerates the returned fields (notice_id, last check time, freshness). It explicitly distinguishes itself from tenders_list_deadline_changes and awards_list_contracts, so an agent can route without opening a 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 explicit sequencing guidance ('Use it first to find a notice_id for tenders_list_deadline_changes'), names the alternative for a different need (awards_list_contracts for contract winners), and states a negative case ('It does not add a watch — ask hello@aurelmark.live').

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.