Skip to main content
Glama
Sign In

More AI - ChatGPT & Claude MCP (Fortnox)

by cloud.amore.accounting
OverviewDiscussionsAdmin

Kontoutdrag och huvudbok

get_account_ledger
Read-onlyIdempotent

Kontoutdrag och huvudbok: verifikationsraderna på ett eller flera konton för en period, med ingående balans, löpande saldo och utgående balans. Example question: "Visa alla verifikationsrader på konto 4010 i mars." Computed on the server from live Fortnox data (Fortnox API, https://api.fortnox.se/apidocs), over all pages.

Input Schema

NameRequiredDescriptionDefault
todateNoÅÅÅÅ-MM-DD Date as YYYY-MM-DD unless the text allows more.
accountNokontonummer, obligatoriskt — ett konto (1930), flera (1930,1940) eller ett intervall (1910-1939 eller en hel kontogrupp 1200-1299), högst 200 konton; av ett int Comma-separated.
fromdateNoÅÅÅÅ-MM-DD Date as YYYY-MM-DD unless the text allows more.
financialyearNoräkenskapsårets id Number.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / account / description
      Previous value: -"kontonummer, obligatoriskt — ett konto (1930), flera (1930,1940) eller ett intervall (1910-1939 eller en hel kontogrupp 1200-1299), högst 200 kontonummer; av et Comma-separated."New value: +"kontonummer, obligatoriskt — ett konto (1930), flera (1930,1940) eller ett intervall (1910-1939 eller en hel kontogrupp 1200-1299), högst 200 konton; av ett int Comma-separated."
  2. Changed5 schema fields changed
    • changedInput schema / properties / account / description
      Previous value: -"kontonummer, obligatoriskt — ett konto (1930), flera (1930,1940) eller ett intervall (1910-1939 eller en hel kontogrupp 1200-1299), högst 200 kontonummer; av et"New value: +"kontonummer, obligatoriskt — ett konto (1930), flera (1930,1940) eller ett intervall (1910-1939 eller en hel kontogrupp 1200-1299), högst 200 kontonummer; av et Comma-separated."
    • changedInput schema / properties / financialyear / description
      Previous value: -"räkenskapsårets id"New value: +"räkenskapsårets id Number."
    • changedInput schema / properties / financialyear / type
      Previous value: -[
-  "string",
-  "number"
-]New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / fromdate / description
      Previous value: -"ÅÅÅÅ-MM-DD"New value: +"ÅÅÅÅ-MM-DD Date as YYYY-MM-DD unless the text allows more."
    • changedInput schema / properties / todate / description
      Previous value: -"ÅÅÅÅ-MM-DD"New value: +"ÅÅÅÅ-MM-DD Date as YYYY-MM-DD unless the text allows more."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context by stating that results are computed server-side from live Fortnox data over all pages, which tells the agent about data freshness and pagination handling.

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 front-loaded with the essential purpose and stays reasonably short. The example question and API source note are useful, though the source link is somewhat less essential.

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 read-only ledger tool with annotations, an output schema, and fully described parameters, the description covers the main behavior and data source. It could be strengthened by clarifying how it differs from similar sibling tools, but nothing critical is missing.

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 input schema already explains the four parameters in detail. The description reinforces that accounts and a period are involved, but adds no syntax or constraints beyond the schema.

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?

Description clearly states that it returns voucher lines for one or more accounts over a period, including opening, running, and closing balances. It is specific about the resource and output but does not distinguish itself from similar siblings such as get_postings_by_account or get_balance_sheet.

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 question ('Visa alla verifikationsrader på konto 4010 i mars') gives a clear usage context. It does not provide explicit exclusions or name alternatives, but the example makes the intended use case understandable.

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