Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

List Fortnox Customers

fortnox_list_customers
Read-onlyIdempotent

Retrieve paginated customer lists from Fortnox accounting, filtering by status, name, or customer number.

Instructions

List customers from Fortnox accounting system.

Retrieves a paginated list of customers with optional filtering by status, name, or customer number.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • filter ('active' | 'inactive'): Filter by customer status

  • search_name (string): Search customers by name (partial match)

  • customer_number (string): Filter by specific customer number

  • organisation_number (string): Filter by organisation number

  • response_format ('markdown' | 'json'): Output format

Returns: List of customers with customer number, name, email, city, and organisation number.

Examples:

  • List all active customers: filter="active"

  • Search by name: search_name="Acme"

  • Get specific customer: customer_number="1001"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
limitNoMaximum number of results to return (1-100)
filterNoFilter by customer status
search_nameNoSearch customers by name (partial match)
customer_numberNoFilter by specific customer number
response_formatNoOutput format: 'markdown' or 'json'markdown
organisation_numberNoFilter by organisation number
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context by mentioning pagination, partial matching for search_name, and the return fields. It does not contradict annotations but also does not go deeply into edge cases, ordering, or rate limits. The added value over annotations is moderate.

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, a Returns section, and examples. It is somewhat lengthy but each section earns its place by clarifying parameters and usage. The information is front-loaded with the purpose, and the formatting makes it easy to scan.

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?

Given the tool's moderate complexity (7 parameters, 2 enums) and the absence of an output schema, the description provides good coverage: it explains pagination, filters, response format, and return fields. It lacks details like default sorting, but for a read-only list tool with strong annotations, this is sufficiently complete.

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%, so the schema already documents all parameters. The description repeats the parameter details in the Args section and adds examples (e.g., filter='active', search_name='Acme') that illustrate usage. However, it does not add new semantic meaning beyond the schema descriptions, such as parameter interactions or format specifics. The baseline of 3 is appropriate.

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 'List customers from Fortnox accounting system' and elaborates on retrieving a paginated list with optional filters. It uses a specific verb+resource structure and distinguishes from sibling tools like fortnox_get_customer (single customer) and fortnox_create_customer (creation).

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 provides clear context for when to use the tool (listing customers) and includes examples of common use cases. However, it does not explicitly contrast it with alternatives like fortnox_get_customer or fortnox_top_customers, nor does it state when not to use it. The 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