Skip to main content
Glama
diblaze

bokio-mcp

by diblaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bokio_chart_of_accounts

Read-only

Lists the company's BAS chart of accounts with account numbers and names, so you can find the account numbers that ledger and balance tools require.

Instructions

List the company's BAS chart of accounts: account numbers with names. Use it to find the account number the ledger and balance tools take; bokio_get_account reads a single account.

Input Schema

NameRequiredDescriptionDefault
queryNoBokio filter query; combine conditions with &&, e.g. "date>=2026-07-01&&date<=2026-07-31"
companyIdNoBokio company id. Defaults to BOKIO_COMPANY_ID if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / properties / companyId / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number (1-based)",
-  "exclusiveMinimum": 0,
-  "maximum": 9007199254740991,
-  "type": "integer"
-}
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Items per page",
-  "exclusiveMinimum": 0,
-  "maximum": 200,
-  "type": "integer"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Bokio filter query; combine conditions with &&, e.g. \"date>=2026-07-01&&date<=2026-07-31\"",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description adds the return shape (numbers with names), which is genuinely useful with no output schema, but says nothing about whether the list is paginated, complete, or static per company. With annotations carrying the safety profile, a 3 is appropriate.

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?

Two compact sentences, front-loaded with the identity of the resource and its payload, followed by usage and the sibling distinction. Zero filler and nothing an agent must read twice.

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?

There is no output schema, and the description partly compensates by stating what comes back (account numbers with names). For a two-optional-param read tool that is nearly complete; the only gap is that the filtering behavior of query is left unexplained.

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 coverage is 100%, so the query and companyId parameters are already documented in the schema, including the BOKIO_COMPANY_ID default. The description adds no meaning beyond that — notably it never mentions that the list can be filtered via the query parameter, which is counterintuitive for a chart of accounts. Baseline 3 is correct when the schema does the work.

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?

States a specific verb and resource ('List the company's BAS chart of accounts') and immediately specifies the payload ('account numbers with names'). It explicitly contrasts itself with the sibling bokio_get_account ('reads a single account'), so an agent can route without opening either schema.

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?

Gives a concrete use case — 'Use it to find the account number the ledger and balance tools take' — which names the downstream consumers and why you'd call this first. It names the single-account alternative, but offers no explicit exclusion or condition for filtering the list, so it falls just short of a full 5.

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

Deploy Server

Other Tools