Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Update Fortnox Account

fortnox_update_account
Idempotent

Update an existing account in the chart of accounts. Provide the account number to modify description, VAT code, active status, cost center settings, or project settings.

Instructions

Update an existing account in the chart of accounts.

Args:

  • account_number (number): Account number to update (required)

  • description (string): Account description

  • vat_code (string): VAT code

  • active (boolean): Whether the account is active

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

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

Returns: The updated account details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoWhether the account is active
vat_codeNoVAT code for the account
descriptionNoAccount description
account_numberYesAccount number to update (required)
response_formatNoOutput format: 'markdown' or 'json'markdown
project_settingsNoProject settings
cost_center_settingsNoCost center settings
Behavior3/5

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

The description adds that it updates an existing account and returns the updated details, which is beyond the annotations. However, it does not disclose whether it performs a partial or full update, error behavior for missing accounts, or any side effects. Annotations already cover idempotency and non-destructiveness.

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 structured and not verbose, with a clear intro, an Args list, and a Returns section. However, the Args list is redundant with the schema and could be trimmed without losing value.

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?

Given the tool's complexity (7 parameters, no output schema) and presence of annotations, the description is minimally adequate. It states the purpose and return value, but lacks detail on partial updates, error handling, and the response_format parameter, leaving notable gaps.

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 description coverage is 100%, so the baseline is 3. The description's Args list repeats schema information without adding new meaning and omits the response_format parameter, providing no semantic value beyond 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 it updates an existing account in the chart of accounts, using a specific verb and resource. This distinguishes it from sibling tools like fortnox_create_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?

No guidance is provided on when to use this tool versus alternatives (e.g., create vs. update, or get vs. update). It does not mention prerequisites like account existence or any conditions for use.

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