Skip to main content
Glama
Sign In

More AI - ChatGPT & Claude MCP (Fortnox)

by cloud.amore.accounting
OverviewDiscussionsAdmin

Kontoplan

get_chart_of_accounts
Read-onlyIdempotent

Kontoplan: bolagets konton per kontoklass, med saldo och momskod. Example question: "Vilka konton har vi? Vilket konto använder vi för frakt?" Computed on the server from live Fortnox data (Fortnox API, https://api.fortnox.se/apidocs), over all pages.

Input Schema

NameRequiredDescriptionDefault
sokNoord i kontots namn, till exempel "frakt"
allaNo"true" för att ta med konton som inte är aktiva
accountNoett konto eller ett intervall, till exempel "1930" eller "1930-1999" (i stället för from_account/to_account) Comma-separated.
to_accountNohögsta kontonummer BAS account number.
from_accountNolägsta kontonummer BAS account number.
financialyearNoräkenskapsårets id; standard det som innehåller i dag Number.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account
      Added value: +{
+  "description": "ett konto eller ett intervall, till exempel \"1930\" eller \"1930-1999\" (i stället för from_account/to_account) Comma-separated.",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  2. Changed7 schema fields changed
    • changedInput schema / properties / alla / type
      Previous value: -[
-  "string",
-  "number"
-]New value: +[
+  "boolean",
+  "string",
+  "number"
+]
    • changedInput schema / properties / financialyear / description
      Previous value: -"räkenskapsårets id; standard det som innehåller i dag"New value: +"räkenskapsårets id; standard det som innehåller i dag Number."
    • changedInput schema / properties / financialyear / type
      Previous value: -[
-  "string",
-  "number"
-]New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / from_account / description
      Previous value: -"lägsta kontonummer"New value: +"lägsta kontonummer BAS account number."
    • changedInput schema / properties / from_account / type
      Previous value: -[
-  "string",
-  "number"
-]New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / to_account / description
      Previous value: -"högsta kontonummer"New value: +"högsta kontonummer BAS account number."
    • changedInput schema / properties / to_account / type
      Previous value: -[
-  "string",
-  "number"
-]New value: +[
+  "number",
+  "string"
+]
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavior beyond that: results are computed server-side from live Fortnox data and cover all pages.

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 short and front-loaded: it identifies the resource and contents first, then gives concrete example questions and source context. There is no filler.

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?

With an output schema, rich parameter descriptions, and annotations covering safety, the description supplies the remaining important context: live Fortnox data and all-page coverage. It could be more complete by clarifying when to choose this over sibling account tools.

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 description coverage is 100%, so the parameters are already well documented in the input schema. The description adds no parameter-level guidance, which is acceptable but not value-adding at the baseline level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource precisely: the company's chart of accounts by account class, including balance and VAT code. It is more specific than the title alone, but it does not distinguish this tool from nearby siblings such as list_accounts or show_fortnox_chart.

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 example questions ('Which accounts do we have?' and 'Which account do we use for freight?') give clear usage context for account lookup. It does not state when not to use the tool or name alternative account-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All More AI - ChatGPT & Claude MCP (Fortnox) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources