Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

Create Fortnox Supplier

fortnox_create_supplier

Create a new supplier in Fortnox with name and optional details like contacts, addresses, and payment terms. Returns the supplier with an assigned supplier number.

Instructions

Create a new supplier in Fortnox.

Args:

  • name (string): Supplier name (required)

  • supplier_number (string): Supplier number (auto-generated if not provided)

  • organisation_number (string): Company registration number

  • email (string): Email address

  • phone (string): Phone number

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

  • currency (string): 3-letter currency code

  • vat_number (string): VAT registration number

  • bank_account (string): Bank account number

  • bg_number (string): Bankgiro number

  • pg_number (string): Plusgiro number

  • terms_of_payment (string): Payment terms code

  • comments (string): Internal comments

Returns: The created supplier with assigned supplier number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity
nameYesSupplier name (required)
emailNoPrimary email address
phoneNoPrimary phone number
countryNoCountry name
address1NoStreet address line 1
address2NoStreet address line 2
commentsNoInternal comments about the supplier
currencyNoCurrency code (e.g., 'SEK', 'EUR')
zip_codeNoPostal/ZIP code
bg_numberNoBankgiro number
pg_numberNoPlusgiro number
vat_numberNoVAT registration number
bank_accountNoBank account number
country_codeNoTwo-letter country code (e.g., 'SE' for Sweden)
response_formatNoOutput format: 'markdown' or 'json'markdown
supplier_numberNoSupplier number (auto-generated if not provided)
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 indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds context by noting that supplier_number is auto-generated if not provided, and that the created supplier with assigned supplier number is returned. It does not contradict annotations and provides useful behavioral details beyond them.

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 well-structured with a clear opening sentence, an Args list, and a Returns section. It is compact given the 19 parameters, with no filler text. However, the parameter list largely repeats the schema descriptions, making it slightly redundant but still efficient.

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 complex tool with 19 parameters and no output schema, the description covers purpose, all parameters, and the return value. It does not address potential error cases or constraints beyond 'required' on name, but it provides sufficient context for an agent to invoke the tool correctly. The absence of an output schema is mitigated by the Returns section.

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 has 100% parameter description coverage, so the schema already explains each parameter. The description lists the parameters with brief clarifiers (e.g., '3-letter currency code') and notes auto-generation, but this mostly duplicates schema content. It adds little new meaning beyond the schema, fitting the baseline for high schema coverage.

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 starts with 'Create a new supplier in Fortnox,' which clearly specifies the action (create), the resource (supplier), and the system (Fortnox). This distinguishes it from sibling tools like update_supplier, delete_supplier, and list_suppliers. The description also summarizes the expected outcome in Returns.

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 clearly indicates this tool is for creating a new supplier, which implies usage when adding a supplier. However, it does not explicitly mention when not to use it, such as when the supplier already exists (in which case update_supplier would be appropriate) or any prerequisites. The context is clear but not elaborated.

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