Skip to main content
Glama

MaxRechnung

Positions-Vorlage anlegen

create_item_template

Tarif: ab Pro (darunter antwortet die API mit plan_required).

Positions-Vorlage anlegen

Positions-Vorlagen sind ab Pro, Positions-Sets und Rechnungsvorlagen ab Business; darunter antwortet der jeweilige Endpunkt mit 403 plan_required.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON-Request-Body.
_idempotency_keyNoOptional. Geht als Header `Idempotency-Key` an die API: derselbe Wert mit demselben Aufruf liefert 24 Stunden lang die erste Antwort zurück, statt den Vorgang zu wiederholen. Bei einem Wiederholversuch denselben Wert schicken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond that: the licensing gate and the exact failure signal (403 plan_required), plus the fact that neighbouring resources (Positions-Sets, Rechnungsvorlagen) sit on a higher tier. It says nothing about what is created on success, side effects on existing sets, or any return value.

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?

The plan-tier information is front-loaded, but it is then restated in a third sentence that partially duplicates the first, and the actual purpose line is a bare copy of the title. Nothing is padded to great length, yet the ordering buries the tool's function behind licensing detail.

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?

For a creation tool with no output schema but a fully documented nested request body, the missing pieces are modest. The licensing gate and its error code are the one thing the schema cannot convey, and the description covers that, though it omits any statement of what a successful call yields.

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 description coverage is 100% and the nested body properties carry detailed semantics (customer_ids replacement and 409 behavior, article_number uniqueness, negative unit_price for discounts), so the schema does the heavy lifting. The description contributes no parameter meaning whatsoever, which is the baseline 3 case.

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 only statement of what the tool does is "Positions-Vorlage anlegen", which is a verbatim restatement of the tool title and adds no information beyond the name. The remaining sentences discuss plan tiers rather than the resource being created or how it differs from siblings such as list_item_templates or create_invoice_from_template.

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?

The description gives a hard precondition (available from the Pro tier onward, otherwise 403 plan_required), which is useful, but there is no when-to-use guidance and no routing to alternatives or related tools (e.g. listing templates first, or adding the template to a set). An agent learns when the call will be rejected, not when it should be preferred.

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