Skip to main content
Glama
easor

easor

by Markku-hur

Get accounting periods

get_accounting_periods
Read-only

Retrieve a customer's accounting periods, optionally with nested bookkeeping periods, filtered by locked status. Use it to list period data for financial reporting.

Instructions

Returns a customer's accounting periods (each with nested bookkeeping periods) from Easor's Organization API. Global — no region-specific path.

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>"
    },
    "name": "get_accounting_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
lockedNoFilter to locked (true) or unlocked (false) periods only
pageSizeNo
pageIndexNo
organizationNumberYesEasor organization/customer number
sortByDateAscendingNo
includeBookkeepingPeriodsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the genuinely useful fact that the endpoint is global with no region-specific path, and discloses that results nest bookkeeping periods. It says nothing, however, about pagination defaults or result-size behavior, which matters for a list endpoint with pageSize/pageIndex.

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 short sentences, front-loaded with the core purpose, and the second sentence carries a distinct routing fact rather than filler. Nothing is redundant.

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

Completeness2/5

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

With six parameters, only one required, 33% schema coverage and no output schema, the definition is thin: it does not characterize the paginated response shape, defaults, or how the optional filters narrow results. An agent can call it but cannot predict the volume or structure of what comes back beyond 'nested bookkeeping periods'.

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?

The description mentions no parameters at all, while schema description coverage is only 33% — locked and organizationNumber are documented in schema, but includeBookkeepingPeriods, sortByDateAscending, pageSize and pageIndex are bare. The phrase 'each with nested bookkeeping periods' hints at the includeBookkeepingPeriods flag but never explains it as a toggle, and pagination/sorting behavior is left entirely undocumented.

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?

The description names a specific verb and resource ('Returns a customer's accounting periods') and adds the useful detail that each period nests bookkeeping periods and comes from the Organization API. It does not explicitly distinguish itself from siblings like get_general_ledger_events, but the resource is concrete enough that an agent can identify it.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. 'Global — no region-specific path' is a routing detail, not usage guidance, so an agent must infer the use case from the name alone.

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