Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

List Fortnox Accounts

fortnox_list_accounts
Read-onlyIdempotent

Retrieve accounts from Fortnox's chart of accounts with filters for account number range or description, enabling targeted financial data extraction.

Instructions

List accounts from the chart of accounts in Fortnox.

Retrieves a paginated list of accounts with optional filtering.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • search_description (string): Search accounts by description

  • from_account (number): Filter accounts from this number (1000-9999)

  • to_account (number): Filter accounts to this number (1000-9999)

  • response_format ('markdown' | 'json'): Output format

Returns: List of accounts with account number, description, and active status.

Examples:

  • List revenue accounts: from_account=3000, to_account=3999

  • List expense accounts: from_account=4000, to_account=8999

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
limitNoMaximum number of results to return (1-100)
to_accountNoFilter accounts to this account number
from_accountNoFilter accounts from this account number
response_formatNoOutput format: 'markdown' or 'json'markdown
search_descriptionNoSearch accounts by description
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral details beyond those annotations: pagination behavior (limit/page), filtering ranges (account numbers 1000-9999), and return shape (account number, description, active status). No contradictions with annotations.

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?

The description is well-organized: a one-sentence summary, a bulleted Args list, a Returns line, and two practical examples. Every section earns its place, and the text is appropriately sized for a tool with six parameters.

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 list tool with no output schema, the description provides all necessary context: pagination, filtering, return fields, and concrete examples. It fully equips an agent to select and invoke the tool correctly.

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%, with every parameter already described in the schema. The description restates the parameters and adds illustrative examples (e.g., 'List revenue accounts: from_account=3000, to_account=3999'), but it does not provide significant additional meaning beyond the schema's existing descriptions.

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 opens with 'List accounts from the chart of accounts in Fortnox,' using a specific verb and resource. It clearly differentiates from sibling tools like fortnox_get_account (single account) and fortnox_create_account/update_account/delete_account (mutations).

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?

The description conveys clear usage context: a paginated list with optional filtering, supported by examples such as 'from_account=3000, to_account=3999' for revenue accounts. It stops short of explicitly naming when to use alternatives (e.g., fortnox_get_account for a single account), but the intended use is unambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erp-mafia/fortnox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server