Skip to main content
Glama

list_items

List/filter items, scoped to the caller's member companies (A1).

Optional period (YYYY-MM) filters by the item's effective date (invoice date, falling back to the Europe/Zurich-local ingestion date); a malformed value returns 422 {"msg": "period must be YYYY-MM"}. exclude_triage_status drops items carrying that triage verdict (NULL-safe; for unrelated not a booked one, ZCT-954).

Optional q: a case-insensitive substring match over the filename and both counterparty names (linked, and extracted data.company).

duplicate filters on the row's is_duplicate flag (ZET-413); credit_note on its is_credit_note flag (ZET-429) — both server-side, so total stays exact. posted filters on the posting badge (ZCT-811): true = posted, false = held, reversed or not booked; a copy filed with the booking of the same invoice ("Already booked", posting.filed_with) is in neither (ZEN-1). overdue (D08-G14): due before today (Zurich), still owing, not a credit note. Owing is the open item's rest; a document with no open item is owing until a bank movement is linked to it (R2-2).

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

Input Schema

NameRequiredDescriptionDefault
qNo
paidNo
limitNo
orderNodate_desc
offsetNo
periodNo
postedNo
sourceNo
overdueNo
directionNo
duplicateNo
company_idNo
credit_noteNo
triage_statusNo
archive_statusNo
analysis_failedNo
counterparty_idNo
exclude_triage_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / order
      Added value: +{
      +  "default": "date_desc",
      +  "enum": [
      +    "date_desc",
      +    "due_asc"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / overdue
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / analysis_failed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  4. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does deliver real behavioral detail: a malformed period yields 422 with a specific message shape, exclude_triage_status is NULL-safe, and duplicate/credit_note filtering is server-side so total stays exact (implying a paginated response with an exact count). It omits whether ordering/pagination defaults matter, what the response envelope looks like, and any permission requirement beyond the member-company scope.

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 scope statement is front-loaded and each paragraph addresses one filter, which is easy to scan. However, a large share of the tokens go to internal ticket identifiers (A1, ZCT-954, ZET-413, ZET-429, ZCT-811, ZEN-1, D08-G14, R2-2) that convey nothing to an agent and inflate the definition.

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 an 18-parameter tool with no annotations and no output schema, the description is materially incomplete: eleven parameters, including several with ambiguous meaning, are left undocumented, and there is no statement of return shape, ordering behavior, or authorization. What is covered is unusually precise, but the coverage gap is too large relative to tool complexity.

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 description coverage is ~0% (only direction and triage_status carry schema text), so the description must compensate, yet it explains only about 7 of 18 parameters: q, period, exclude_triage_status, duplicate, credit_note, posted, overdue. Significant filters such as paid, source, archive_status, analysis_failed, company_id, counterparty_id, limit/offset and order are given no meaning beyond their names, including some whose semantics are non-obvious (paid vs posted, analysis_failed).

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?

"List/filter items, scoped to the caller's member companies (A1)" gives a specific verb plus resource plus an explicit scope constraint, which tells an agent exactly what universe it queries. It does not name any sibling (e.g. get_item, global_search, list_gl_open_items) or say how it differs from them, keeping it out of 5 territory.

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 description explains filter mechanics but never states when to reach for this tool instead of alternatives such as global_search or the GL/AR list endpoints, nor any prerequisite for calling it. Usage is only implied by the list semantics, which matches the 'no guidance' band.

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