Skip to main content
Glama

MaxRechnung

Eigene Felder auflisten

list_custom_fields
Read-only

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

Eigene Felder auflisten

Alle eigenen Felder des Kontos in der Reihenfolge der App: Schlüssel, Typ, Auswahlwerte und Bereiche. Angelegt und geändert werden sie in der App unter Einstellungen → Eigene Felder. Ohne Blättern (höchstens 50 Felder).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 genuine value on top: results come back in app display order, there is no pagination, and the response is capped at 50 fields — constraints an agent needs to know to avoid requesting further pages or expecting more data.

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?

The content is short and mostly front-loaded, with the plan-compatibility note and the no-pagination limit each stated once. The repeated heading line 'Eigene Felder auflisten' immediately after the plan line is redundant with the title and earns no place.

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?

There is no output schema, so the description carries the burden of describing return values and does so by listing the fields each record exposes plus the 50-item cap and ordering. Combined with the read-only annotations, an agent has enough to call this correctly; only an explicit pointer to a mutation path is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly says nothing about inputs and instead spends its words on scope and output shape.

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 names a specific verb and resource ('Eigene Felder auflisten', 'Alle eigenen Felder des Kontos') and enumerates what each entry contains: Schlüssel, Typ, Auswahlwerte und Bereiche. It is unambiguous what the tool does, though the heading merely restates the title and no sibling is named to sharpen the boundary.

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?

It implicitly steers usage by stating that fields are created and modified in the app under Einstellungen → Eigene Felder, which tells the agent this tool is read-only and that mutations are out of scope here. However, it never states an explicit alternative tool or a when-not condition, leaving the routing inference to the reader.

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