Skip to main content
Glama

ausfuellen_fortsetzen

Resume form filling after court confirmation by applying the human-confirmed procedural court and completing the application up to the data overview.

Instructions

Nach status 'gericht_bestaetigen': das vom Menschen bestätigte Prozessgericht übernehmen und bis zur Datenübersicht weiterfüllen. Der Name muss genau dem angezeigten Gericht entsprechen.

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": {
      "prozessgericht_bestaetigt": "<prozessgericht_bestaetigt>"
    },
    "name": "ausfuellen_fortsetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
prozessgericht_bestaetigtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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=true, so the mutation/open-world profile is covered. The description adds that it writes confirmed data forward until the Datenübersicht and that the value must match exactly the displayed court, but says nothing about what happens on a mismatch, whether partial progress is lost, or what state results.

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?

Two sentences with the precondition front-loaded and the validation constraint second; no filler. Slightly cryptic phrasing ('bis zur Datenübersicht weiterfüllen') leaves the endpoint of the action implicit.

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 resume-style mutation tool with a single required param, no output schema and no annotations beyond safety flags, the description covers the entry condition and the value constraint but not the outcome — what gets written, how far it fills, or error behavior on mismatch. Adequate but with a clear gap around results.

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 0% for the single required parameter 'prozessgericht_bestaetigt', so the description must carry the burden. It does add two useful constraints — the value is the human-confirmed court and must exactly equal the displayed court name — but does not specify format, case sensitivity, or what a mismatch returns.

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 ('übernehmen', 'weiterfüllen') and resource (Prozessgericht, form data through to the Datenübersicht), and ties it to a concrete workflow status 'gericht_bestaetigen'. An agent can distinguish it from the sibling portal_ausfuellen (initial filling) by the explicit continuation/resume framing, though the description never names that sibling directly.

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

Usage Guidelines4/5

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

Gives an explicit trigger condition — only after status 'gericht_bestaetigen' — which is a real when-to-use rule rather than implied usage. It does not explicitly exclude alternatives (e.g., when to call portal_ausfuellen instead), keeping it short of a 5.

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