Skip to main content
Glama

Vinka

Verifikat

lista_verifikat
Read-onlyIdempotent

Listar bokförda verifikat för ett räkenskapsår, valfritt en månad. 50 per sida.

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": "lista_verifikat"
  }
}

Input Schema

NameRequiredDescriptionDefault
arNoÅret då räkenskapsåret slutar, t.ex. 2026
sidaNo
manadNo
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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely new behavioral fact, the 50-per-page result size, but says nothing about ordering, what the 'sida' cursor does past the last page, or how a bad year is handled.

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, zero filler, with the resource and filter scope front-loaded and pagination last. Every clause earns its place.

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 and rich annotations, the description need only cover filtering and paging, which it does. Minor gaps remain around default fiscal year when 'ar' is omitted (no parameters are required) and result ordering.

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 only 50%, with 'sida' and 'manad' undocumented in the schema; the description compensates by indicating the optional month filter and the page size that gives 'sida' meaning. It also anchors 'ar' to the fiscal year, adding clarity beyond the schema's own note.

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?

States a specific verb and resource ('Listar bokförda verifikat') plus scope ('för ett räkenskapsår, valfritt en månad'). The 'listar' vs the sibling 'hamta_verifikat' distinction is implicit rather than stated, so it stops 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?

Usage is implied by the scope: fiscal year, optional month narrowing, and paginated results. There is no explicit 'when to use this vs hamta_verifikat' routing or statement of prerequisites, so guidance remains inferred.

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.