swiss-efv-mcp

Overview Schema Source Related Servers Discussions Admin

Dump Status

dump_status

Read-onlyIdempotent

Check cache freshness and upstream health for Swiss federal finance datasets, replacing deprecated status checks with the fiscal_status namespace.

Instructions

DEPRECATED — use fiscal_status. Kept as an alias for backward compatibility; will be removed in a future minor release.

Reports cache freshness and upstream health per dataset (SEC-022: every tool now shares the fiscal_ server-identity namespace).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`source`	No	Data: Eidgenoessische Finanzverwaltung EFV — opendata.swiss (OGD Schweiz, frei nutzbar). Private, non-affiliated project. Kein Anspruch auf Vollstaendigkeit.
`healthy`	Yes
`message`	Yes
`datasets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Jul 31, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond that: alias behavior, deprecation status, removal timeline, and the SEC-022 server-identity namespace note. No contradiction exists.

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

Conciseness4/5

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

The description is compact and front-loaded with the deprecation warning. The SEC-022 parenthetical is mildly tangential, but the overall structure is efficient and easy to scan.

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?

Given zero parameters, an output schema, and a clear alias relationship to fiscal_status, the description covers everything an agent needs: what the tool reports, that it is deprecated, and where to route usage instead.

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 has zero parameters and an empty schema, so the baseline is 4. The description adds no parameter-specific detail, but none is needed since the schema fully documents that the tool takes no inputs.

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?

The description clearly identifies the tool as a deprecated alias and states its function: 'Reports cache freshness and upstream health per dataset.' It also names the replacement, fiscal_status, which distinguishes it from the sibling tools.

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?

It explicitly says 'DEPRECATED — use fiscal_status' and warns it will be removed in a future minor release. This gives unambiguous guidance on when not to use this tool and which alternative to select.

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

Deploy Server