Skip to main content
Glama

Vinka

Resultaträkning

resultatrakning
Read-onlyIdempotent

Resultaträkningen för en period: intäkter, kostnader och resultat. Standard: räkenskapsårets början till 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": "resultatrakning"
  }
}

Input Schema

NameRequiredDescriptionDefault
slutNoTill och med, ÅÅÅÅ-MM-DD
startNoFrån och med, ÅÅÅÅ-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 establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the default date range when start/slut are omitted, which is genuinely useful behavior beyond the annotations, but says nothing about aggregation level, accounting basis, or whether figures are inclusive of VAT.

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 no filler: the returned content is front-loaded and the default behavior follows immediately. Nothing in the text is redundant with 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?

With no output schema, the description carries the burden of describing returns and does so by naming the three line-item categories. For a three-parameter, all-optional read-only report tool this is largely sufficient; a note on whether results are summed or itemized would close the remaining gap.

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%, and the schema itself documents the ÅÅÅÅ-MM-DD format plus that bolag_id comes from lista_bolag and is only needed with multiple companies. The description goes beyond that by stating what happens when the date parameters are absent, giving the default-range semantics the schema does not express.

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 specific resource (resultaträkning) and enumerates its contents — intäkter, kostnader och resultat — so an agent knows exactly what it returns. It does not explicitly contrast itself with the sibling balansrakning, which is the closest confusable alternative, so it falls short of 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 default period (fiscal year start to today) implies the typical usage of pulling a period report, but there is no explicit statement of when to choose this over balansrakning or huvudbok, nor any prerequisites. Usage is inferable from the content list rather than stated.

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.