Skip to main content
Glama

Belege auflisten

list_documents
Read-only

Belege auflisten (neueste zuerst, 50 je Seite). Filter nach Art und Suchbegriff (Kunde oder Nummer); mit updated_since nur seitdem Geänderte, mit fields nur id/updated_at.

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

Input Schema

NameRequiredDescriptionDefault
qNo
pageNo
typeNo
fieldsNonur diese Felder, 500 je Seite — zum Abgleich von ID-Listen
updated_sinceNonur seit diesem Zeitpunkt geänderte (ISO 8601, einschließlich); sortiert dann nach updated_at, id aufsteigend

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "nur diese Felder, 500 je Seite — zum Abgleich von ID-Listen",
      +  "enum": [
      +    "id",
      +    "updated_at",
      +    "id,updated_at"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / updated_since
      Added value: +{
      +  "description": "nur seit diesem Zeitpunkt geänderte (ISO 8601, einschließlich); sortiert dann nach updated_at, id aufsteigend",
      +  "format": "date-time",
      +  "type": "string"
      +}
  2. 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 openWorldHint=false, so the safety profile is covered; the description adds genuine behavioral detail beyond that: default ordering (newest first), default page size of 50, keyword matching against customer or number, and the fact that updated_since changes the sort order. It still omits the returned document shape and how paging terminates, which keeps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one dense sentence front-loads the most important facts (what it lists, ordering, page size) and then handles the filters. There is no filler, though the stacked parentheticals and semicolon clauses make it slightly harder to parse than a short bulleted phrasing would be.

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 no output schema, the essentials an agent needs to call it correctly are present: pagination size, ordering, filter semantics, and the incremental-sync mode. Missing pieces are the shape of a returned document and page-exhaustion behavior, which are minor for a no-required-parameter list call.

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?

Schema coverage is only 40% (q, page and type have no schema descriptions), so the description must compensate and largely does: it explains that the search term matches customer or number, that type filters by document kind, and that fields restricts output to id/updated_at. The page parameter is left unexplained, which is the remaining gap.

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 states a specific verb and resource ('Belege auflisten') plus scope details (newest first, 50 per page, filterable by type and search term). It is unambiguous about what is returned, but it never contrasts itself with sibling list tools such as list_contracts or list_customers, and it does not distinguish itself from get_document for single-record retrieval.

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?

Usage is implied rather than stated: filtering by 'Art und Suchbegriff' and using updated_since for incremental sync are described as capabilities, which suggests when to use them. However, there is no explicit 'use this instead of X' routing, no guidance on when to prefer get_document, and no note on what to do when results exceed one page.

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