Skip to main content
Glama
diblaze

bokio-mcp

bokio_open_items

Read-only

Lists unpaid items on a ledger account as of a date, matches payments FIFO by exact amount, and returns open items with age, unmatched payments, and balance.

Instructions

List unpaid items on a ledger account at asOf, matching each payment to the earliest unpaid posting of the same amount (FIFO, exact öre). Returns open items with their age in days, payments that matched nothing, the balance, and the oldest loaded year's opening balance as one unitemised amount. Amounts in ledger sign: debit positive, credit negative.

Input Schema

NameRequiredDescriptionDefault
asOfNoDate to evaluate at (YYYY-MM-DD); defaults to today.
accountNoLedger account; default 1510 (receivables), 2440 for supplier debt.
companyIdNoBokio company id. Defaults to BOKIO_COMPANY_ID if omitted.
lookbackYearsNoCalendar years before the year of asOf to load, so older unpaid items are itemised; default 1.

Output Schema

NameRequiredDescriptionDefault
asOfYes
openYes
accountYes
balanceYes
openingUnitemisedYes
unmatchedPaymentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / account / description
      Added value: +"Ledger account; default 1510 (receivables), 2440 for supplier debt."
    • changedInput schema / properties / asOf / description
      Previous value: -"Defaults to today"New value: +"Date to evaluate at (YYYY-MM-DD); defaults to today."
    • addedInput schema / properties / lookbackYears / description
      Added value: +"Calendar years before the year of asOf to load, so older unpaid items are itemised; default 1."
  2. Addedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds substantial behavioral context beyond that: the FIFO exact-öre matching algorithm, that unmatched payments are returned, that items include age in days, that the oldest loaded year's opening balance is presented as one unitemised amount, and the ledger sign convention. This is rich disclosure for a read-only tool.

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?

The description is three tightly written sentences: purpose and matching semantics first, then return contents, then sign convention. Every sentence contributes useful information and nothing is wasted.

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

Completeness5/5

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

Given that an output schema exists and annotations cover the safety profile, the description is complete enough: it explains the matching logic, what is returned, and how amounts are signed. No critical information for correct invocation 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 100%, so all four parameters are already documented in the input schema, including defaults and examples. The description adds interpretation context (ledger sign, exact-öre matching) but does not add parameter-specific meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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—listing unpaid ledger items at a given date—and includes the distinctive FIFO matching semantics (exact öre). This clearly differentiates it from siblings like bokio_account_ledger (all entries) and bokio_account_balances (balances), so an agent can identify the tool without opening the schema.

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 by the purpose: it is the tool for open items / aging at a point in time. However, the description never explicitly says when to choose this over alternatives such as bokio_account_ledger or bokio_reconcile_bank, nor does it state any exclusions or prerequisites. This is adequate but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.