Skip to main content
Glama

list_gl_journal_entries

List journal entries.

period_ids narrows to specific fiscal periods, and is how a caller asks for one fiscal year: the year's period ids (ZET-285). Without it the route lists every fiscal year. total is the filtered total.

untagged_subledger_control=true narrows to the entries that posted to an AR/AP control account without touching the subledger, under allow_untagged_control (ZET-150) — the postings a subledger-vs-control divergence traces back to.

origin: one entry origin (ZEN-42). account_id: entries with a line on it; date_from/date_to: posting date; amount_min/amount_max: the entry total.

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

Input Schema

NameRequiredDescriptionDefault
qNo
sortNoposting_date
limitNo
orderNodesc
offsetNo
originNo
statusNo
date_toNo
date_fromNo
account_idNo
amount_maxNo
amount_minNo
company_idYes
period_idsNo
coding_guessedNo
untagged_subledger_controlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / coding_guessed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / amount_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / amount_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / date_from
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / date_to
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / origin
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "human",
      +        "system",
      +        "ai",
      +        "api",
      +        "mcp",
      +        "chat"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does disclose meaningful behavior: the unfiltered default spans every fiscal year, total is the filtered total, and untagged_subledger_control targets control-side postings without subledger lines. It omits pagination/ordering behavior, result shape, and any permission or volume warnings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Paragraphs are grouped per filter cluster and front-loaded with the highest-value rule (period_ids equals one fiscal year). Sentences are dense but each carries a distinct fact; ticket references like ZET-285 are minor noise but do not impede comprehension.

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

Completeness3/5

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

For a 16-parameter listing tool with no annotations and no output schema, the description covers the distinctive filters but leaves several parameters (q, status, coding_guessed, sort/order/limit/offset) undocumented and says nothing about return shape or pagination. An agent could call it correctly for the explained filters but would be guessing on the rest.

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 0%, so the description must compensate, and it does so for the non-obvious parameters: period_ids carries a fiscal-year idiom, origin is a single entry origin, account_id matches entries with a line, date_from/date_to are posting dates, amount_min/amount_max are entry totals, and untagged_subledger_control is explained in domain terms. Gaps remain for q (presumably free-text search), status, and coding_guessed, which are left entirely to inference.

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 journal entries" gives a specific verb and resource, and the following paragraphs make clear this is a filtered listing of GL journal entries rather than bank entries or AR invoices. It never explicitly contrasts itself with siblings such as list_bank_entries, but the resource is concrete enough to distinguish it.

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 gives useful usage context: without period_ids the route lists every fiscal year, and period_ids is the way to scope to one fiscal year; untagged_subledger_control is for divergence tracing. However, there is no explicit when-to-use/when-not-to-use guidance relative to the sibling tools (e.g. get_gl_account_ledger or gl_trial_balance), only filter-level guidance.

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