Skip to main content
Glama
Sign In
arbeitsagentur-mcp

arbeitsagentur-mcp

by slopmaxxer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

registration_deadlines

Read-onlyIdempotent

Calculates legal deadlines to register as job-seeking or unemployed under SGB III using your employment end date and the date you learned of it.

Instructions

Deadlines to register as job-seeking (§ 38 SGB III) and as unemployed (§ 141 SGB III).

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

Input Schema

NameRequiredDescriptionDefault
learned_onNoDay the end became known (notice received); default from profile or today
employment_endNoLast day of employment; default from profile

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds only domain framing (the two statutory bases), saying nothing about defaults, computation behavior, or how results relate to profile dates. With annotation coverage the bar is lower, so a 3 is appropriate.

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?

A single sentence with zero filler, front-loading the resource before the statutory qualifiers. Nothing to trim.

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, so return values needn't be explained, and both parameters are well documented in the schema. The description covers the tool's scope adequately; only the usage/exclusion guidance is absent.

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

Parameters3/5

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

Schema description coverage is 100%, and both parameters (learned_on, employment_end) carry their own default behavior notes. The description adds no syntax or meaning beyond the schema, so the baseline 3 applies.

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?

States a specific resource (registration deadlines) and splits it into two distinct legal cases, §§ 38 and 141 SGB III. An agent can tell it apart from siblings like objection_deadline, calculate_deadline, and unemployment_benefit_duration. It stops short of 5 because it doesn't explicitly contrast those siblings.

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 description gives no when-to-use guidance, no prerequisites (e.g. that it needs an employment end date), and names no alternatives. Usage is only implied by the concept of registration deadlines.

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