Skip to main content
Glama
Sign In
arbeitsagentur-mcp

arbeitsagentur-mcp

by slopmaxxer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

log_correspondence

Record letters, decisions, emails, calls, and meetings with the agency or Jobcenter, and automatically calculate and track the Widerspruch deadline for incoming Bescheide.

Instructions

Record a letter, decision, e-mail, call or meeting with the agency / Jobcenter.

For an incoming Bescheid the Widerspruch deadline is calculated and tracked automatically.

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": {
      "date": "<date>",
      "kind": "<kind>",
      "subject": "<subject>"
    },
    "name": "log_correspondence"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate of the letter (as printed on it) or of the call/visit
kindYes'bescheid' = formal decision (gets a Widerspruch deadline), 'anhoerung' = hearing before a sanction
notesNo
channelNo
subjectYesWhat it is about, e.g. 'Bewilligung Arbeitslosengeld' or 'Sperrzeit 1 Woche'
summaryNo
reply_byNoDeadline stated in the letter (Anhörung, Aufforderung); creates a task
directionNoeingang
file_pathNoPath to a scan/PDF of the document
referenceNoAktenzeichen / Zeichen
counterpartNoOffice / person
received_onNoActual day of receipt if later than usual (keep the envelope)
legal_remedy_instruction_okNofalse if the Bescheid has no or a wrong Rechtsbehelfsbelehrung

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), but the description adds a genuine side effect beyond them: an incoming Bescheid automatically triggers Widerspruch deadline calculation and tracking. That is exactly the kind of non-obvious behavior an agent needs; other side effects (e.g., task creation) are only visible via the schema.

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?

Two tight sentences, front-loaded with purpose and followed by the key behavioral caveat. No filler; every clause earns its place.

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 need not be described. For a 13-parameter logging tool the description conveys purpose and the main side effect, though it says nothing about the numerous optional fields (channel, file_path, reference, etc.) beyond what the schema already covers.

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 69%, so most parameters are already documented. The description only implicitly ties 'Bescheid' to the deadline behavior, adding no syntax or format detail beyond what the schema provides, 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?

The description states a clear verb+resource ('Record a letter, decision, e-mail, call or meeting'), so an agent understands this creates a correspondence entry. It does not explicitly distinguish itself from siblings like list_correspondence or update_correspondence, so the 'record/create' intent is implied rather than contrasted.

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 only implied – 'Record' suggests a create operation and the second sentence hints at when deadline tracking matters (incoming Bescheid). There are no explicit when-to-use/when-not statements or references to the neighboring update_correspondence / list_correspondence tools.

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