Skip to main content
Glama

Vinka

Balansräkning

balansrakning
Read-onlyIdempotent

Tillgångar, skulder och eget kapital per ett datum. Standard: i dag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "balansrakning"
  }
}

Input Schema

NameRequiredDescriptionDefault
datumNoÅÅÅÅ-MM-DD
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds one behavioral fact not in the annotations, the today-by-default date, but says nothing about report scope, rounding or freshness beyond that.

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?

Two short sentences with the report contents and the default front-loaded, and zero filler or repetition of the title.

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 report tool with full schema coverage and no output schema, the description usefully enumerates what the report contains, which partially substitutes for a return-value description. Minor gaps remain around how the balance sheet is scoped or formatted, but nothing essential to invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the default-date semantics for datum that the schema does not encode (there is no default field). It does not elaborate on bolag_id beyond what the schema already says.

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 exact content returned (assets, liabilities and equity as of a date), which maps unambiguously to a balance sheet and lets an agent distinguish it in substance from resultatrakning. It stops short of an explicit verb or of naming a sibling, so a 4 rather than a 5.

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 only usage cue is the default date behavior ("Standard: i dag"), which implies you can call it with no arguments for a current balance sheet. There is no explicit guidance on when to prefer this over resultatrakning or huvudbok, leaving the choice to inference from the content described.

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.