fiken-mcp

fiken_list_accounts

Read-only

Retrieve bookkeeping accounts for the current year. Filter by account code range for precise results.

Instructions

Retrieves bookkeeping accounts for the current year

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": "fiken_list_accounts"
  }
}

Input Schema

Name	Required	Description
`page`	No
`pageSize`	No
`toAccount`	No	Filter to account code
`fromAccount`	No	Filter from account code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 30, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, and the description aligns with a read operation. The description adds 'for the current year' as a scoping detail, but does not disclose pagination or filtering behavior, which are important for a listing 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?

Single sentence of 8 words. Front-loaded with verb and resource. No unnecessary text.

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 4 parameters, no output schema, and low schema coverage, the description is insufficient. It omits pagination, filtering, and return format. Among account-related siblings, no distinction is provided.

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 adds no meaning about parameters. Schema coverage is 50% (only two parameters have descriptions), so the description should compensate but does not mention page, pageSize, toAccount, or fromAccount.

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 clearly states the action ('Retrieves') and resource ('bookkeeping accounts') with a specific scope ('for the current year'). This distinguishes it from sibling tools like fiken_get_account (single account) and fiken_list_account_balances.

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 guidance on when to use this tool vs alternatives (e.g., fiken_get_account for a specific account, fiken_list_account_balances for balances). No mention of prerequisites or common use cases.

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

Deploy Server