Skip to main content
Glama
io.github.mohammad-abbasi-sh/feiertage-mcp

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

feiertage_health

Probe whether the feiertage-api.de endpoint is reachable and report status ok, blocked, or error with the HTTP code and probed URL, so you can confirm the API is up before querying holidays.

Instructions

Check whether the feiertage-api.de 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": "feiertage_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains the possible status values (ok, blocked, error), maps them to HTTP codes, and discloses that it makes one polite request without fetching listings. It does not mention authentication requirements or retry behavior, but for a no-parameter health check this is largely sufficient.

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?

The description is short, front-loaded with the core action, and every sentence adds value. It explains the status meanings and the no-fetch behavior without unnecessary detail.

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 that an output schema exists, the description need not fully document return values, yet it still summarizes the key outcomes. For a zero-parameter health check, everything an agent needs to call and interpret the tool is present.

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, so the baseline is 4. The description appropriately does not discuss parameters and focuses on return semantics instead.

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 uses a specific verb and resource: 'Check whether the feiertage-api.de API is reachable right now.' It also explicitly distinguishes itself from sibling data-fetching tools by stating 'it does not fetch any listings.' An agent can immediately tell this is a health probe, not a holiday lookup.

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

Usage Guidelines4/5

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

The description implies when to use it: to verify API reachability and distinguish bot-wall/rate-limit responses from generic errors. It does not explicitly name alternatives or state exclusions, but the contrast with siblings is clear from the 'does not fetch any listings' clause.

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