Skip to main content
Glama
erp-mafia

Fortnox MCP Server

by erp-mafia

List Fortnox Supplier Invoices

fortnox_list_supplier_invoices
Read-onlyIdempotent

Retrieve supplier invoices from Fortnox with filters for status, supplier, date, and amount. Get paginated accounts payable results for analysis.

Instructions

List supplier invoices (accounts payable) from Fortnox.

Retrieves a paginated list of supplier invoices with optional filtering by status, supplier, date range, or amount.

Args:

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

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

  • filter ('cancelled' | 'fullypaid' | 'unpaid' | 'unpaidoverdue' | 'unbooked' | 'pendingpayment'): Filter by invoice status

  • supplier_number (string): Filter by supplier number

  • from_date (string): Filter invoices from this date (YYYY-MM-DD)

  • to_date (string): Filter invoices to this date (YYYY-MM-DD)

  • period ('today' | 'yesterday' | ... | 'last_year'): Convenience date period, overrides from_date/to_date

  • from_final_pay_date (string): Filter by due date from (YYYY-MM-DD)

  • to_final_pay_date (string): Filter by due date to (YYYY-MM-DD)

  • sortby ('suppliername' | 'suppliernumber' | 'invoicenumber' | 'invoicedate' | 'total'): Field to sort by

  • sortorder ('ascending' | 'descending'): Sort order (default: ascending)

  • fetch_all (boolean): Fetch all results by auto-paginating (max 10,000 results)

  • min_amount (number): Filter invoices >= this amount (client-side)

  • max_amount (number): Filter invoices <= this amount (client-side)

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

Returns: List of supplier invoices with supplier, dates, amounts, and status.

Examples:

  • List unpaid supplier invoices: filter="unpaid"

  • Last month's supplier invoices: period="last_month"

  • Supplier invoices this year: supplier_number="1", period="this_year"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
limitNoMaximum number of results to return (1-100)
filterNoFilter supplier invoices by status
periodNoConvenience date period filter (e.g., 'last_month', 'this_quarter'). Overrides from_date/to_date if provided.
sortbyNoField to sort results by
to_dateNoFilter invoices to this date (YYYY-MM-DD)
fetch_allNoFetch all results by auto-paginating through all pages. WARNING: May take time for large datasets (max 10,000 results).
from_dateNoFilter invoices from this date (YYYY-MM-DD)
sortorderNoSort order for resultsascending
max_amountNoFilter invoices with total <= this amount (client-side filter)
min_amountNoFilter invoices with total >= this amount (client-side filter)
response_formatNoOutput format: 'markdown' or 'json'markdown
supplier_numberNoFilter by supplier number
to_final_pay_dateNoFilter by due date to (YYYY-MM-DD)
from_final_pay_dateNoFilter by due date from (YYYY-MM-DD)
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral details beyond annotations: pagination, fetch_all auto-pagination with a 10,000-result cap, client-side vs. server-side filtering (min_amount/max_amount), and response format options. No contradiction with annotations.

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 neatly organized with a summary, Args list, Returns section, and Examples. It is long but appropriately so for 15 parameters, and every part contributes actionable information with no filler or redundancy.

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

Completeness5/5

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

The description fully equips an agent to invoke the tool correctly: it explains all parameters, return content (supplier, dates, amounts, status), pagination behavior, filter semantics, client-side filtering, and provides concrete examples. Since there is no output schema, the description's Return section compensates well.

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?

Input schema coverage is 100% with each property having a rich description. The description's Args section mostly mirrors the schema, only adding minor clarifications like 'period overrides from_date/to_date' and 'client-side' for amount filters. It does not substantially enhance understanding 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 uses a specific verb 'List' and a precise resource 'supplier invoices (accounts payable) from Fortnox', which clearly distinguishes it from sibling tools like fortnox_list_invoices (which likely lists customer invoices) and fortnox_list_suppliers. It also communicates the tool's scope with optional filtering and pagination.

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

Usage Guidelines4/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 status filters, date ranges, and examples like 'filter="unpaid"' and 'period="last_month"'. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous enough for selection.

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