Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Create Fortnox Account

fortnox_create_account

Create a new account in the Fortnox chart of accounts. Specify account number and description, plus optional VAT code, cost center, and project settings to structure financial tracking.

Instructions

Create a new account in the chart of accounts.

Args:

  • account_number (number): Account number 1000-9999 (required)

  • description (string): Account description (required)

  • vat_code (string): VAT code for the account

  • active (boolean): Whether the account is active (default: true)

  • cost_center_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Cost center settings

  • project_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Project settings

  • sru_code (number): SRU code for tax reporting

Returns: The created account details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoWhether the account is active
sru_codeNoSRU code for tax reporting
vat_codeNoVAT code for the account
descriptionYesAccount description (required)
account_numberYesAccount number (1000-9999, required)
response_formatNoOutput format: 'markdown' or 'json'markdown
project_settingsNoProject settings for the account
cost_center_settingsNoCost center settings for the account
Behavior3/5

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description adds that it returns the created account details, but offers no additional context on permissions, validation, or side effects. Minor added value beyond 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 description is concise and well-structured, with a clear main sentence and an Args list. It is slightly redundant with the schema but does not waste words.

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?

With eight parameters and no output schema, the description should more thoroughly describe the return value and any business rules. The return statement 'The created account details' is vague, and no mention is made of uniqueness or other constraints. The description is adequate but not comprehensive.

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%, meaning the input schema already describes all parameters. The description restates the parameters with types and constraints but adds no new semantic insight beyond what is in the schema.

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 tool creates a new account in the chart of accounts, using a specific verb and resource. This distinguishes it from sibling tools like fortnox_update_account, fortnox_delete_account, and fortnox_get_account.

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?

The description does not provide guidance on when to use this tool versus alternatives. It merely states 'Create a new account' without mentioning conditions, exclusions, or other tools like fortnox_update_account for modifications.

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