Skip to main content
Glama

MaxRechnung

Beleg lesen

get_sales_document
Read-only

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

Beleg lesen

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_sales_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` des Belegs (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `AN-2026-0004`) liefert `GET /sales-documents?number=…` (MCP: `list_sales_documents` mit `number`) die `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's only added behavioral fact is the plan availability ("in jedem Tarif"), which is marginal. It says nothing about what a document record contains, error behavior for an unknown UUID, or whether drafts/cancelled documents are included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the tariff line, but the second line is pure repetition of the title and therefore does not earn its place. Brevity here reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema and no annotations beyond safety flags, the description should at minimum say what a Beleg is and what the call returns. Neither is covered, so an agent must infer the retrieval semantics from the name alone.

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 description contributes nothing about the single id parameter, but schema description coverage is 100% and the schema itself carefully explains UUID vs. document number and how to resolve one to the other. With the schema carrying the full burden, the baseline of 3 applies.

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

Purpose2/5

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

The description's only content about the operation is "Beleg lesen", which restates the tool title verbatim and adds no detail about what reading a document actually returns or covers. The other line concerns plan availability, not purpose, so an agent learns nothing beyond the name itself.

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 indication of how this differs from siblings like list_sales_documents, download_sales_document_pdf, or get_invoice, and no stated preconditions. The genuinely useful routing hint (fetch the internal id via list_sales_documents with number) lives in the input schema, not the description.

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