Skip to main content
Glama
Sign In

More AI - ChatGPT & Claude MCP (Fortnox)

by cloud.amore.accounting
OverviewDiscussionsAdmin

Läs flera underlag i ett anrop

read_documents
Read-onlyIdempotent

Läs flera underlag i ett anrop: belopp, datum, leverantör, fakturanummer, OCR och bankgiro för varje fil i en inkorgsmapp eller en lista med filer. Example question: "Vad står det på fakturorna som ligger i inkorgen?" Computed on the server from live Fortnox data (Fortnox API, https://api.fortnox.se/apidocs), over all pages.

Input Schema

NameRequiredDescriptionDefault
idsNovalfritt: filernas id, kommaseparerade (högst 40) — i stället för hela mappen, eller för att fortsätta med remaining Comma-separated.
mappNoinkorgens mapp: inbox_s (leverantörsfakturor, standard), inbox_v (verifikationer), inbox_ku (kvitto och utlägg), inbox_d (dagskassa) One of: inbox_s, inbox_v, inbox_ku, inbox_d.
namnNovalfritt: del av filnamnet (sok och filnamn betyder samma sak); bara de filer i mappen vars namn innehåller texten läses

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / namn
      Added value: +{
+  "description": "valfritt: del av filnamnet (sok och filnamn betyder samma sak); bara de filer i mappen vars namn innehåller texten läses",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / ids / description
      Previous value: -"valfritt: filernas id, kommaseparerade (högst 40) — i stället för hela mappen, eller för att fortsätta med remaining"New value: +"valfritt: filernas id, kommaseparerade (högst 40) — i stället för hela mappen, eller för att fortsätta med remaining Comma-separated."
    • changedInput schema / properties / mapp / description
      Previous value: -"inkorgens mapp: inbox_s (leverantörsfakturor, standard), inbox_v (verifikationer), inbox_ku (kvitto och utlägg), inbox_d (dagskassa)"New value: +"inkorgens mapp: inbox_s (leverantörsfakturor, standard), inbox_v (verifikationer), inbox_ku (kvitto och utlägg), inbox_d (dagskassa) One of: inbox_s, inbox_v, inbox_ku, inbox_d."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: extraction is computed server-side from live Fortnox data and spans all pages, which tells the agent it need not paginate manually and that results reflect real-time data.

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 definition is short and front-loaded: purpose, returned fields, example, then data source. Minor waste from the mixed Swedish/English phrasing ('Example question:'), but no sentence is redundant.

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?

With an output schema present, the description does not need to explain return values, yet it still summarizes the key fields, and it covers the two things an agent would otherwise guess wrong: server-side computation and full pagination. Nothing essential for correct invocation 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%, including the folder enum values and the 40-id cap, so the schema does the heavy lifting. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema is fully documented.

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 opens with a specific verb and resource ('Läs flera underlag i ett anrop') and enumerates the extracted fields (belopp, datum, leverantör, fakturanummer, OCR, bankgiro), so the agent knows exactly what it gets back. It distinguishes batch reading from single-file reads only implicitly via 'flera ... i ett anrop', without naming the sibling read_inbox_file.

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 example question ('Vad står det på fakturorna som ligger i inkorgen?') gives a concrete usage scenario, and the ids/mapp/namn params imply folder-wide vs. targeted reads. However, there is no explicit when-not guidance and no routing to read_inbox_file, list_unprocessed_inbox, or get_inbox for single-file or listing use cases.

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