Skip to main content
Glama

Stand einer Übernahme

import_status
Read-only

Wie weit ist eine laufende Übernahme? Kennung aus import_starten. Am Ende steht der Bericht: was übersprungen wurde und was der Kunde wissen muss (Formulare, alter Zeichensatz, Adressen, die auf die alte Website zeigen).

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": {
      "run": "<run>"
    },
    "name": "import_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYesKennung aus import_starten

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful substance beyond that by describing what the final report reveals: skipped items, forms, legacy character sets, and addresses still pointing at the old site. It stops short of explaining progress semantics, such as whether the call is polled or how a completed run is signalled.

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?

Three short sentences with the core question front-loaded and no filler. The parenthetical enumeration of report contents is dense but each item carries information for the agent.

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?

With one required parameter, full schema coverage, and no output schema, the description carries the return-value burden and does so by sketching the report contents. What is missing is minor: nothing is said about async completion behaviour or how often to re-query.

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?

There is only one parameter and schema coverage is 100%, so the baseline is a 3. The description essentially repeats the schema's own wording about the identifier coming from import_starten and adds no format, validity, or reuse detail beyond it.

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 opens with a specific question about the progress of a running import, which names the resource and the operation clearly. The reference to 'Kennung aus import_starten' ties it to a distinct sibling, making the pairing obvious even without an explicit contrast sentence.

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?

It implies the tool is used after starting an import and tells the agent where the required identifier comes from, which is a real usage precondition. However, it gives no explicit when-not guidance or contrast with sibling status tools such as publish_status, so the routing is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources