Skip to main content
Glama
easor

easor

by Markku-hur

Get used chart of accounts

get_used_chart_of_accounts
Read-only

Retrieve the bookkeeping accounts used by an organization within a date range to support accounting reports, reconciliations, and financial analysis.

Instructions

Returns the bookkeeping accounts used within a date range.

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": {
      "organizationNumber": "<organizationNumber>",
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "get_used_chart_of_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateYesYYYY-MM-DD
fromDateYesYYYY-MM-DD
organizationNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. Beyond that the description adds almost nothing: it does not clarify what 'used' means (accounts with postings in the period versus all accounts in the chart), whether zero-activity accounts appear, or how results are ordered or paginated.

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?

One short, front-loaded sentence with no wasted wording. Its brevity is achieved by omission rather than by tight packaging of real information.

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 three-required-parameter read tool with annotations covering safety and no output schema, the definition is minimally sufficient but thin. The key semantic ambiguity, what 'used' means in terms of accounting activity, and the unexplained organizationNumber parameter leave real gaps.

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 coverage is 67%: fromDate and toDate are documented as YYYY-MM-DD, but organizationNumber has no description anywhere. The description restates the date-range notion without adding format, required-ness, or organization-scoping meaning beyond the schema.

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?

A specific verb (Returns) and resource (bookkeeping accounts used) with a stated scope (within a date range). The word 'used' hints at a distinction from the sibling lookup_chart_of_accounts_template, but the description never spells out that contrast.

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?

No explicit when-to-use or when-not-to-use guidance, and no mention of the sibling lookup_chart_of_accounts_template, which an agent would naturally weigh against this tool. The date-range scoping only implies the filtering dimension of usage.

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