Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Update Fortnox Supplier

fortnox_update_supplier
Idempotent

Update supplier details in Fortnox by specifying the supplier number and any fields to change. Returns the updated supplier record.

Instructions

Update an existing supplier in Fortnox.

Args:

  • supplier_number (string): Supplier number to update (required)

  • All other fields from create_supplier (only provided fields are updated)

Returns: The updated supplier details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity
nameNoSupplier name
emailNoPrimary email address
phoneNoPrimary phone number
activeNoWhether the supplier is active
countryNoCountry name
address1NoStreet address line 1
address2NoStreet address line 2
commentsNoInternal comments
zip_codeNoPostal/ZIP code
bg_numberNoBankgiro number
pg_numberNoPlusgiro number
bank_accountNoBank account number
response_formatNoOutput format: 'markdown' or 'json'markdown
supplier_numberYesSupplier number to update (required)
terms_of_paymentNoPayment terms code
organisation_numberNoOrganisation/company number
Behavior4/5

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

Annotations already cover read/write nature, idempotency, and destructiveness. The description adds key behavioral detail: 'only provided fields are updated' (partial update semantics) and states that it returns the updated supplier details. This goes beyond what annotations provide, though it does not mention auth requirements or error handling.

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 concise and front-loaded, using one sentence for the purpose and brief bullet-like lines for parameters and return value. It avoids redundant explanations and stays within a few lines.

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

Completeness4/5

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

For a 17-parameter tool with complete schema descriptions and useful annotations, the description is adequately complete. It covers the essential behavioral aspects (partial update, return value) but relies on referencing create_supplier for field details. Since the schema lists all fields, this is acceptable; a fully self-contained description would have been slightly better.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all 17 parameters, so the baseline is 3. The description adds meaningful semantic context by highlighting that supplier_number is required and that all other fields are optional with partial update behavior. This clarifies the effect of omitting fields, which the schema alone does not convey.

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 'Update an existing supplier in Fortnox' with a specific verb and resource. It distinguishes from sibling tools like create_supplier and delete_supplier by focusing on the update operation and noting that only provided fields are updated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (updating an existing supplier) but does not explicitly mention when to use this tool instead of create_supplier or delete_supplier. It also does not provide exclusions or alternative tool references, so guidance is implied rather than explicit.

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