Skip to main content
Glama
Sign In
arbeitsagentur-mcp

arbeitsagentur-mcp

by slopmaxxer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

public_holidays

Read-onlyIdempotent

Retrieve statutory holidays for a given year and German state to support accurate deadline calculations. Use the result to identify non-working days when managing applications and case deadlines.

Instructions

Public holidays relevant for deadline calculations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
stateNoBundesland; default from profile, else nationwide only

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, covering the safety profile for a lookup. The description adds nothing behavioral beyond that — no note on how state defaults are resolved, whether results are cached, or how nationwide vs. regional holidays are returned. An output schema exists, but the description still contributes no extra context.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though the terseness is close to under-specification rather than optimal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two params, one required) and an output schema covers return values, so the bar is low. Still, the description omits that holidays are German/Bundesland-scoped and never mentions the year/state lookup, leaving the agent to reconstruct context from the schema alone.

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

Parameters2/5

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

Schema description coverage is only 50%: the 'year' parameter has no schema description and no documentation in the description, and the description doesn't explain the semantics of year or state either. With a low coverage rate the description should compensate but does not, so meaning is missing for half the inputs.

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?

Names a specific resource (public holidays) and ties it to a concrete use (deadline calculations), so an agent knows what it returns. It lacks a verb and doesn't contrast itself against siblings like calculate_deadline or registration_deadlines, but the resource is unambiguous enough to distinguish it.

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

Usage Guidelines2/5

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

The phrase 'relevant for deadline calculations' hints at a use case but never states when to call this tool, in what order relative to calculate_deadline, or whether it should be used standalone. There are no exclusions or alternatives named, so the agent must infer the workflow.

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

Deploy Server

Other Tools