io.github.mohammad-abbasi-sh/ecb-mcp

ecb_health

Checks if the ECB SDMX API is reachable right now, returning status ok, blocked, or error with the HTTP status and probed URL.

Instructions

Check whether the ECB SDMX API is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it maps return states (ok = HTTP 200, blocked = 403/429 from a bot wall or rate limit, error) and notes the load profile ('one polite request'). What is missing is any guidance on what the agent should do when it receives 'blocked' (back off, retry interval), which matters for a probe designed to gate further calls.

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?

Three short sentences, front-loaded with the purpose, then the return contract, then the load/scope caveat. Every sentence earns its place and nothing is repeated from the name.

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?

An output schema exists, yet the description still usefully explains the status meanings, which is the key information for acting on the result. For a zero-parameter health probe this covers everything needed to invoke it correctly; the only gap is a recommended response to the 'blocked' state.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless tool applies. The description correctly presents this as a no-argument probe.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Check whether the ECB SDMX API is reachable right now.' The closing clause 'it does not fetch any listings' implicitly distinguishes it from the data-fetching siblings (bond yields, exchange rates, etc.), but no sibling is named explicitly, so differentiation relies on inference.

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

Usage Guidelines3/5

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

Usage context is implied — this is a diagnostic probe you would run before or when a data query fails — but the description never says 'use this when X fails' or 'do not use this to fetch data.' No alternatives or exclusions are spelled out, leaving the agent to infer the when-to-use condition.

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

Deploy Server