Skip to main content
Glama
Sign In
arbeitsagentur-mcp

arbeitsagentur-mcp

by slopinger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

meineba_leistungen

Read-onlyIdempotent

Retrieve granted benefits and payment entries from Meine BA to check eligibility outcomes and current disbursements.

Instructions

Granted benefits and payments as shown in Meine BA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that the data mirrors what is displayed in the Meine BA portal, hinting it depends on a logged-in session, but it never states the auth requirement or what happens when no session exists.

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 clause with no filler and the resource front-loaded. It is terse and efficient, though its brevity edges toward 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?

For a zero-parameter read tool with no output schema, the description is only marginally sufficient: it conveys what data comes back but omits the login/session prerequisite implied by the surrounding meineba_login_* siblings. An agent could plausibly call it without a session and fail.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the result set is unfiltered (all granted benefits and payments).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (granted benefits and payments) and the data source (Meine BA), which is meaningful, but supplies no verb at all – it is unclear whether this lists, summarizes, or details records. It also does not distinguish itself from siblings like meineba_antraege or meineba_status, leaving the agent to infer the boundary.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as meineba_antraege for applications or meineba_verlauf for history. The agent must guess when this tool is the right choice.

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