Skip to main content
Glama
Sign In

Aurelmark

by io.github.Ishan73744
OverviewDiscussionsAdmin

List EU funding call changes

funding_list_changes
Read-onlyIdempotent

Returns changes to open and forthcoming EU grant calls on the official EU Funding & Tenders Portal: new calls, moved deadlines, status changes and removals, with before/after records. Use it to follow EU grants; use tenders_list_deadline_changes for procurement tenders and compliance_list_deadlines for legal compliance dates. Inputs (all optional, they narrow together): since (YYYY-MM-DD, default 7 days ago), change (added/amended/removed), field (which field changed, e.g. deadlines), identifier (topic or call id prefix, 2 to 200 characters, e.g. HORIZON-CL5-2026), limit (1 to 50, default 20) and cursor (next_cursor, same filters). Output: changes[] with before and after topic records, official topic URL and observed_at, plus count, has_more, next_cursor and feed check time; the Portal is checked about every 6 hours. A change feed, not a catalogue of all open calls. For one topic's current record use HTTP GET /v1/eu/funding/topics/{id} (see /openapi.json). 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": "funding_list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoOnly changes to this field Allowed: deadlines, status, opens, deadline_model, title, call_title, kind, url; e.g. deadlines.
limitNoChanges per page, 1 to 50 (default 20); e.g. 20.
sinceNoChanges observed on or after this date, YYYY-MM-DD (default: 7 days ago); e.g. 2026-10-01. Must be a parseable YYYY-MM-DD date.
changeNoOne kind of change only Allowed: added, amended, removed; e.g. added.
cursorNoOpaque next_cursor from this tool's prior answer; f followed by 1 to 12 digits, e.g. f0. Keep filters unchanged; omit on first call.
identifierNoTopic/call identifier prefix, 2 to 200 ASCII letters/digits or . _ -, e.g. HORIZON-CL5-2026; omit for all topics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/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, but the description adds substantial context beyond them: refresh cadence ('the Portal is checked about every 6 hours'), pagination behavior via next_cursor, before/after record structure, and the metering/free-tier policy including how errors and empty answers are billed. These are behaviors an agent cannot infer from the annotations or schema.

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 well — purpose, siblings, inputs, output — in a compact sequence. However, the final third is a long preamble about free answers, metering, sanctions-search exceptions, prepaid-credit policy and API keys that is largely policy boilerplate repeated across tools rather than call-specific value, which dilutes an otherwise tight definition.

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?

Despite having no output schema, the description fully documents the return payload (changes[] with before/after topic records, official topic URL, observed_at, count, has_more, next_cursor, feed check time). Combined with freshness cadence, pagination rules, filter conjunction semantics and named alternatives, an agent has everything needed to call it correctly on the first attempt.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: it labels all inputs optional and states they 'narrow together' (conjunctive AND filtering), and repeats the cursor rule 'same filters' to prevent filter drift during paging. It does not add format or syntax detail beyond what the schema already gives for each parameter.

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 changes to open and forthcoming EU grant calls on the official EU Funding & Tenders Portal') and immediately enumerates the change types: new calls, moved deadlines, status changes, removals. It explicitly distinguishes itself from siblings by naming tenders_list_deadline_changes and compliance_list_deadlines for adjacent domains.

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?

Explicit routing guidance: 'Use it to follow EU grants; use tenders_list_deadline_changes for procurement tenders and compliance_list_deadlines for legal compliance dates.' It also states the negative case ('A change feed, not a catalogue of all open calls') and points to the HTTP endpoint for a single topic's current record, so the agent knows both when to use it and when not to.

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