Skip to main content
Glama
easor

easor

by Markku-hur

Look up Easor's generic chart-of-accounts template

lookup_chart_of_accounts_template
Read-only

Look up Easor’s generic Finnish chart-of-accounts template to identify relevant account numbers and group paths; use it for structure, then verify actual balances in live organizational data.

Instructions

Looks up Easor's generic (organization-independent) Finnish chart-of-accounts template — a static reference bundled with this server, not a live API call. Use it to find which account numbers/groups are structurally relevant to a question (e.g. fixed vs. variable costs, which mainCategory alone cannot distinguish), NOT as a source of actual balances — always confirm real figures against the organization's own live data (get_used_chart_of_accounts / get_general_ledger_events / build_profit_and_loss_statement) since an organization's real chart can differ from this template. Pass listGroups:true alone to explore the group hierarchy first; otherwise filter by accountNumber (exact), accountNumberPrefix, nameContains, and/or groupContains (matches any segment of the account's group path, e.g. "MUUTTUVA" for variable-cost groups, "KIINTEÄ" for fixed-cost groups) — at least one filter is required. When presenting a grouped report — balance sheet (tase) or income statement (tuloslaskelma) alike, or anything else grouped by account — use groupPath's own names VERBATIM as section headings/structure — do not paraphrase, translate, or invent your own category labels.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_chart_of_accounts_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 100)
listGroupsNoReturn the distinct group-path hierarchy instead of individual accounts
nameContainsNoCase-insensitive substring match against the account name
accountNumberNoExact account number match
groupContainsNoCase-insensitive substring match against any segment of the account's group path
accountNumberPrefixNoAccount number starts-with match, e.g. "5" for all 5xxx accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial context beyond them: the data is static and organization-independent, real organizational charts can differ from this template, and at least one filter is mandatory. It also prescribes verbatim use of groupPath names when presenting grouped reports, which is behavioral guidance not present in annotations.

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 information is front-loaded and every sentence carries substance, but it is delivered as one dense paragraph with nested parentheticals and em-dashes that could be broken into clearer sections. No filler is present, but the wall-of-text formatting slightly hurts scanability.

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?

For a read-only, six-parameter static-reference tool with no output schema, the description covers what it returns conceptually (accounts and group paths), how to explore the hierarchy, how to filter, when not to rely on it, and how to present grouped results. Nothing an agent needs in order to invoke it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: groupContains matches any segment of the group path with concrete examples ('MUUTTUVA' for variable-cost groups, 'KIINTEÄ' for fixed-cost groups), listGroups:true alone explores the hierarchy, and at least one filter is required. Those additions go beyond the schema's per-field text.

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 ('looks up Easor's generic Finnish chart-of-accounts template') and immediately distinguishes it from live-data siblings by calling it a static reference bundled with the server. An agent can tell it apart from get_used_chart_of_accounts or get_general_ledger_events without opening any schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use ('find which account numbers/groups are structurally relevant'), when-not-to-use ('NOT as a source of actual balances'), and names the alternatives to use instead (get_used_chart_of_accounts / get_general_ledger_events / build_profit_and_loss_statement). It also explains the listGroups:true exploration path and the at-least-one-filter requirement.

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