Skip to main content
Glama

MaxRechnung

Positions-Vorlagen auflisten

list_item_templates
Read-only

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

Positions-Vorlagen auflisten

Gespeicherte Positionen (Beschreibung, Einheit, Menge, Preis, USt.-Satz). Mit customer_id nur die für diesen Kunden sinnvollen: die ihm zugeordneten plus die allgemeinen.

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

Input Schema

NameRequiredDescriptionDefault
limitNoQuery-Parameter limit
offsetNoQuery-Parameter offset
customer_idNoUUID eines Kunden → dessen Vorlagen + allgemeine; `none` → nur allgemeine; leer → alle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the tool is available on every plan (Free, Pro, Business) and the returned fields are enumerated, which an agent cannot infer from the schema. It does not mention ordering of results or pagination behaviour, keeping it short of a 5.

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 content is short, but the resource name is repeated as a standalone line matching the title, and the "Tarif:" plan note is front-loaded ahead of the actual purpose, which inverts priority. A tighter structure would lead with what is listed and fold the plan note later; still, no sentence is wasted enough to drop below 3.

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 read-only listing tool with 3 optional parameters and no output schema, the description covers availability, returned fields and the customer-scoping rule, which is enough to call it correctly. Missing only minor operational details such as result ordering, which the schema's limit/offset already largely imply.

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%, so the schema already defines limit, offset and customer_id including the `none` and empty-string cases. The description restates the customer_id filtering rule (assigned + general) without adding format, edge cases or interaction details beyond what the schema says. Baseline 3 applies when the schema does the heavy lifting.

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+resource ("Positions-Vorlagen auflisten") and then names the actual payload — stored line items with description, unit, quantity, price and VAT rate — so an agent knows what entity is being listed. It does not explicitly distinguish itself from sibling listing tools such as list_item_template_sets or list_invoice_templates, leaving that separation to be inferred from the entity name.

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?

The customer_id clause implicitly tells the agent when to use which mode (per-customer vs. all templates), which is useful usage framing. However there is no explicit "use this instead of X" routing, no prerequisites, and no stated exclusions, so guidance remains implied rather than directive.

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