Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Create Fortnox Customer

fortnox_create_customer

Create a new customer in Fortnox, entering contact, address, VAT, currency, and payment information.

Instructions

Create a new customer in Fortnox.

Args:

  • name (string): Customer name (required)

  • customer_number (string): Customer number (auto-generated if not provided)

  • organisation_number (string): Company registration number

  • email (string): Primary email address

  • phone (string): Primary phone number

  • address1, address2, zip_code, city, country, country_code: Address fields

  • currency (string): 3-letter currency code (e.g., 'SEK')

  • vat_number (string): VAT registration number

  • vat_type ('SEVAT' | 'EUVAT' | 'EUREVERSEDVAT' | 'EXPORT'): VAT type

  • terms_of_payment (string): Payment terms code

  • price_list (string): Price list code

  • comments (string): Internal comments

Returns: The created customer with assigned customer number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity
nameYesCustomer name (required)
emailNoPrimary email address
phoneNoPrimary phone number
countryNoCountry name
address1NoStreet address line 1
address2NoStreet address line 2
commentsNoInternal comments about the customer
currencyNoCurrency code (e.g., 'SEK', 'EUR')
vat_typeNoVAT type for the customer
zip_codeNoPostal/ZIP code
price_listNoPrice list code
vat_numberNoVAT registration number
country_codeNoTwo-letter country code (e.g., 'SE' for Sweden)
customer_numberNoCustomer number (auto-generated if not provided)
response_formatNoOutput format: 'markdown' or 'json'markdown
terms_of_paymentNoPayment terms code
organisation_numberNoOrganisation/company number
Behavior3/5

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

The description adds useful behavioral context such as 'customer_number auto-generated if not provided' and 'Returns: The created customer with assigned customer number.' It does not contradict the annotations, which already indicate non-read-only and non-idempotent behavior, but it does not deepen the explanation of side effects or prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with an Args list and Returns section, but the Args block largely duplicates the information available in the input schema. While it is readable and front-loaded with the main purpose, the redundancy prevents it from being exceptionally concise.

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 create tool with no output schema, the description adequately explains the return value and the auto-generation of customer numbers. It is sufficiently complete given the rich input schema and annotations, though it could mention permission requirements or idempotency caveats.

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?

The input schema already provides descriptions for all 18 parameters (100% coverage). The description restates these parameters and adds minimal semantic value, such as grouping address fields and giving an example currency code. This does not meaningfully exceed what the schema already provides.

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 begins with 'Create a new customer in Fortnox,' which is a specific verb+resource statement. It clearly distinguishes this tool from sibling tools like fortnox_update_customer, fortnox_delete_customer, and fortnox_get_customer.

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 for creating a new customer, but it does not explicitly state when not to use it or mention alternatives. For example, it does not say 'use fortnox_update_customer for existing customers.' Usage context is only implied.

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