Skip to main content
Glama

list_gl_open_items

One page of the AR/AP subledger (member read).

direction filters server-side (ZCT-577); omit it for both. commercial_document_id narrows to one document's item (D09-G13); not with as_of.

as_of (ZCT-577) reconstructs each item's open amount from posted journal lines dated on or before that date, instead of reading today's cached amount. Items are considered regardless of their current status (one settled since that date was open on it), so status is refused alongside it rather than silently ignored. original_amount and status on each row remain the item's own, current facts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "list_gl_open_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
limitNo
offsetNo
statusNo
directionNo
company_idYes
counterparty_idNo
commercial_document_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / counterparty_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 21,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / commercial_document_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 21,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "enum": [
      +        "open",
      +        "partial",
      +        "settled",
      +        "overdue",
      +        "written_off",
      +        "cancelled"
      +      ],
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it explains that as_of recomputes open amounts from journal lines rather than reading cached values, that items are considered regardless of current status, and that a conflicting combination raises an error instead of being silently ignored. It stops short of stating permission requirements beyond 'member read' or any rate/result-size behavior.

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 text is front-loaded and organized by parameter, which makes scanning easy. Minor waste comes from embedded internal reference codes (ZCT-577, D09-G13) that carry no meaning for an agent selecting or calling the tool.

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 an 8-parameter, annotation-free, output-schema-free tool, the description covers the risky semantics well, including a note on what row fields (original_amount, status) represent relative to as_of. Gaps remain around the overall row shape, paging behavior past the first page, and authorization, but nothing essential to a correct call is missing.

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 0% across 8 parameters, so the description must compensate; it explains the genuinely ambiguous ones (direction, as_of, commercial_document_id, status interactions) well. It adds nothing for company_id, counterparty_id, limit, or offset, whose meaning has to be inferred from names and JSON-schema defaults.

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 first sentence names a specific resource — one page of the AR/AP subledger — and marks it as a read ('member read'), so the verb and scope are legible. It does not, however, distinguish itself from siblings such as list_items, list_ar_invoices, or get_gl_account_ledger, so an agent must infer that this is the open-item view rather than any general item list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Genuinely useful conditional guidance is given for parameter combinations: omit direction for both sides, don't pair commercial_document_id with as_of, and status is refused alongside as_of. What is missing is any statement of when to choose this tool over its sibling listers, so the guidance is intra-tool rather than inter-tool.

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