Skip to main content
Glama

Vinka

Bokslut och deklaration

bokslut_och_deklaration
Read-onlyIdempotent

Status för årsredovisning och inkomstdeklaration (eller NE-bilaga och INK4) för ett räkenskapsår: utkast, inlämnad och sista 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": "bokslut_och_deklaration"
  }
}

Input Schema

NameRequiredDescriptionDefault
arNo
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.6/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower. The description does add real value by enumerating the returned states (utkast, inlämnad, sista dag) and the document types covered, which annotations cannot convey. It stops short of explaining what happens when no declaration is registered or how the status is sourced.

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?

A single sentence that front-loads the resource, then the scope, then the returned states. Nothing is redundant and nothing is missing that would fit without padding.

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 status tool with two optional parameters and no output schema, the description conveys both the covered document types and the shape of the answer (draft / submitted / deadline). The only meaningful gap is the format of ar, which the description flags conceptually but does not specify.

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%: bolag_id is fully documented in the schema with its source and conditional use, but ar has no schema description. The description compensates only partially by indicating that the parameter denotes a fiscal year (räkenskapsår), while leaving the accepted format (calendar year, fiscal-year start, or '2024/2025') ambiguous.

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 both resources (årsredovisning and inkomstdeklaration, with NE-bilaga/INK4 variants) and states the scope as a fiscal year, so an agent knows this is a year-end reporting status lookup. It never names a sibling, but none of the listed siblings appear to overlap this domain, so disambiguation is largely unnecessary.

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?

Usage is only implied: an agent can infer this is the tool for checking closing/declaration status for a given year. There is no explicit when-to-use, no exclusions, and no guidance on whether it should be checked before or after related tools like resultatrakning or balansrakning.

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.