Skip to main content
Glama
Sign In
arbeitsagentur-mcp

arbeitsagentur-mcp

by slopinger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_task

Record to-dos and obligations from your Kooperationsplan or Eingliederungsvereinbarung, including title, due date, notes, and source.

Instructions

Add a to-do / obligation (e.g. from the Eingliederungsvereinbarung / Kooperationsplan).

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": {
      "title": "<title>"
    },
    "name": "add_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo
notesNo
titleYesWhat to do, e.g. 'Lebenslauf an Vermittlerin schicken'
sourceNoWhere the duty comes from, e.g. 'Kooperationsplan vom 01.10.2026'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write/safe/closed-world profile is covered. The description adds no behavioral context beyond that (no side effects, duplicate handling, or permission notes). With annotations carrying the safety profile, this is adequate but adds nothing.

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 front-loaded sentence with zero waste; the core action leads and the parenthetical example is genuinely informative.

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?

An output schema exists so return values need no explanation, and annotations cover safety. Still, for a mutation tool the description omits usage guidance and leaves half the parameters undocumented, so it is only minimally complete.

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 coverage is only 50% – title and source are documented in the schema, while due and notes are not documented anywhere. The description's reference to the source document (Eingliederungsvereinbarung/Kooperationsplan) loosely maps to the source param but adds no format or syntax detail to compensate for the gap.

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 verb (add) and resource (to-do/obligation) with a concrete example context (Eingliederungsvereinbarung/Kooperationsplan). Clear what it does, but does not differentiate from siblings like add_appointment or log_correspondence.

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?

No when-to-use, when-not-to-use, or alternative guidance. The domain example implies it is for obligations from official plans, but an agent gets no routing help among the many sibling creation 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