Skip to main content
Glama

Vinka

Huvudbok för ett konto

huvudbok
Read-onlyIdempotent

Transaktionerna på ett konto under en period, med saldo. Använd t.ex. för 'vad har dragits på 1930 i mars?'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "konto": "<konto>"
    },
    "name": "huvudbok"
  }
}

Input Schema

NameRequiredDescriptionDefault
slutNo
kontoYesBAS-konto, t.ex. 1930
startNo
bolag_idNoBolagets id från lista_bolag. Behövs bara om du har flera bolag hos Vinka.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds that results come with a balance ('med saldo'), which is genuine behavioral context about the response. It says nothing about ordering, pagination, or what happens when a period is omitted.

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?

Two short sentences with the core meaning front-loaded, followed by a compact example that earns its place by showing the intended query shape. No redundant restatement of the title or annotations.

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?

There is no output schema, so the description carries the burden of describing returns; it does note that a balance accompanies the transactions. It is close to complete for a simple read tool, with the main remaining gap being date-format and period-default behavior for the two undocumented parameters.

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 50%: konto and bolag_id are documented in the schema, while start and slut are bare strings. The phrase 'under en period' plus the 'i mars' example signals that start/slut define a period, but no accepted date format or default window is given, leaving the undocumented half only partially compensated.

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 names the concrete resource and scope: transactions on one account for a period, including the balance. That is a specific, actionable purpose. It does not explicitly contrast itself with nearby siblings such as lista_verifikat or balansrakning, so differentiation is only implied by the account-and-period framing.

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 har dragits på 1930 i mars?' gives a concrete usage scenario, which implies when the tool applies. There is no explicit when-not guidance, no mention of alternatives for listing vouchers versus a single account ledger, and no prerequisites beyond what the schema states.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.