Skip to main content
Glama

Adressen auflisten

address_list
Read-only

Listet die Adressen im Partner-Adressbuch. Optional nach Name, Stadt oder Mandant gefiltert. EN: Lists the addresses in the partner address book. Optionally filtered by name, city or client.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNoVersatz für die Seitennavigation. Standard 0. EN: Offset for pagination. Default 0.
reasoningNo
searchQueryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Versatz für die Seitennavigation. Standard 0. EN: Offset for pagination. Default 0.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the scope ('Partner-Adressbuch') and the optional filtering behavior, but says nothing about pagination semantics, result volume, or ordering.

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 core sentence is front-loaded and efficient, but the full German/English duplication doubles the length without adding information. Not padded with fluff beyond the translation redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with no output schema and 25% schema coverage, the description should clarify limit bounds, the meaning of reasoning, and how searchQuery maps to name/city/client. Those gaps leave an agent guessing on half the inputs.

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

Parameters2/5

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

Schema coverage is only 25% — only 'offset' is documented in the schema. The description's mention of name/city/client filtering loosely maps to 'searchQuery', but 'limit' (capped at 200) and especially 'reasoning' are left entirely unexplained in both schema and description.

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 and resource ('Listet die Adressen im Partner-Adressbuch') and adds the available filter dimensions. It doesn't explicitly contrast itself with the sibling address_search_company, so an agent must infer that this is the plain listing tool versus the company-search tool.

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?

Only implied usage: 'optionally filtered by name, city or client' hints at when to add filters, but there is no statement of when to use this versus address_search_company, address_validate, or the paginated behavior. No exclusions or prerequisites are given.

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.