Skip to main content
Glama

MaxRechnung

Kunden auflisten

list_customers
Read-only

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

Kunden auflisten

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

Input Schema

NameRequiredDescriptionDefault
limitNoQuery-Parameter limit
offsetNoQuery-Parameter offset
custom_fieldsNoFilter nach eigenen Feldern: `custom_fields[schlüssel]=wert`, mehrere sind UND-verknüpft. Ja/Nein: `true` oder `false` (nicht gesetzt). Unbekannter Schlüssel → `400`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 safety profile is covered. The description contributes only tier availability, which is marginal; it says nothing about pagination behavior, result ordering, default result set size, or what happens with an unknown custom field key (the schema hints at a 400 but the description does not elaborate).

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?

Two short fragments with no filler, so length is fine. However, the least important information (plan availability) is front-loaded ahead of the purpose, and the second line merely echoes the title.

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 read-only list tool with fully documented parameters and annotations covering its safety profile, the definition is functionally sufficient, with no output schema required.

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 limit, offset, and the custom_fields filter syntax are already fully documented in the schema. The description adds no parameter meaning beyond that, which is acceptable at this coverage level but earns no credit.

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?

"Kunden auflisten" is a verbatim restatement of the tool name and title, so the description adds no independent statement of purpose. Nothing distinguishes it from sibling list tools (list_invoices, list_custom_fields, etc.) or explains what a listed customer record contains.

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 guidance given is plan availability ("in jedem Tarif"), which is not usage guidance. There is no indication of when to use this versus create_customer, delete_customer, or any other list tool, and no prerequisites or exclusions are stated.

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