Skip to main content
Glama

MaxRechnung

Sets auflisten

list_item_template_sets
Read-only

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

Sets auflisten

Ein Set bündelt mehrere Positions-Vorlagen mit eigener Menge; eingefügt wird in der gespeicherten Reihenfolge.

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

Input Schema

NameRequiredDescriptionDefault
limitNoQuery-Parameter limit
offsetNoQuery-Parameter offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds plan availability across tiers and the semantics of a set (bundled templates, saved insertion order), but says nothing about pagination behavior or what the listing returns.

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?

Very short and front-loaded, with no filler sentences. The opening fragment "Tarif: in jedem Tarif (Free, Pro, Business)." is slightly awkward and repetitive, but it costs little.

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 simple two-parameter read-only listing tool with a complete schema and safe annotations, the definition is nearly sufficient. The remaining gap is what a returned set looks like, which matters slightly since there is no output schema.

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 coverage is 100% with limit and offset fully described in the schema, so the baseline is 3. The description contributes nothing about ordering, defaults, or how offset interacts with the stated save order.

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 uses "Sets auflisten" (list sets) and adds a definition of what a set is: it bundles multiple line-item templates with their own quantity, inserted in saved order. The verb and resource are specific, though it never distinguishes this tool from sibling listing tools such as list_item_templates.

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 only contextual statement is "Tarif: in jedem Tarif (Free, Pro, Business)" — plan availability, not usage guidance. There is no indication of when to call this instead of create_item_template or list_item_templates, nor any prerequisite or exclusion.

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