Skip to main content
Glama

MaxRechnung

Stand eines asynchronen Auftrags (ZUGFeRD-Erzeugung)

get_job
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Stand eines asynchronen Auftrags (ZUGFeRD-Erzeugung)

Liefert den Stand eines Jobs aus 202-Antworten (bisher nur type: zugferd). status: queued → processing → done (dann download_url) oder failed. Wiederholungen nach Fehlern laufen automatisch und zeigen sich als queued.

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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses the full status lifecycle (queued → processing → done/failed), that download_url appears only on done, and that automatic retries surface as `queued` again — genuinely useful behavioral context for a polling tool. It stops short of polling-interval/backoff advice or how long jobs are retained.

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?

Content is dense and mostly front-loaded, with the state machine summarized compactly in one sentence. The leading 'Tarif: in jedem Tarif (Free, Pro, Business)' line plus a purpose line that duplicates the tool title is mild redundancy but small in size.

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?

Since there is no output schema, the description carries the return-value burden and does so: it names `status`, its possible values, and `download_url` on success. It is nearly complete for a one-parameter polling tool; only polling cadence and handling of long-expired job ids are unaddressed.

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?

The single parameter `id` is already documented at 100% schema coverage, though the schema text is only 'Pfad-Parameter id'. The description adds the meaningful origin of that id (it comes from a `202` response) but does not restate its type or format, so it adds modest value over the schema.

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 and resource ('Liefert den Stand eines Jobs') and narrows scope with 'aus `202`-Antworten (bisher nur `type: zugferd`)', which tells an agent exactly which jobs this covers. It does not explicitly point at sibling tools such as download_invoice_zugferd as the alternative path, so differentiation is implied rather than stated.

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?

The description gives clear triggering context: use it on the job reference returned in a `202` response, and only for `type: zugferd` jobs today. It also indicates the terminal condition (done → download_url). No explicit when-not guidance or named alternative for retrieving the resulting document, which keeps it below a 5.

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