Skip to main content
Glama

Vinka

Moms

moms
Read-onlyIdempotent

Utan period: bolagets momsperioder med belopp, status och förfallodatum. Med period (t.ex. 2026-Q3 eller 2026-09): momsrapporten med rutorna och vad som ska betalas.

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

Input Schema

NameRequiredDescriptionDefault
periodNoPeriodnyckel från listan, t.ex. 2026-Q3
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds the important behavioral fact that the tool is dual-mode and that the response content differs by mode (period list vs. tax-box report). With no output schema, that return-shape disclosure is genuinely valuable. It does not discuss pagination, history depth, or how far back periods are listed.

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 parallel clauses, one per mode, each front-loaded with the condition ('Utan period' / 'Med period'). No filler, no redundancy, and the mode split is immediately scannable.

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 return values and does so for both modes, listing the concrete fields an agent would get. Combined with 100% parameter coverage and read-only annotations, an agent has enough to call it correctly. Minor gap: nothing about period history range or 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 100%, so the baseline is 3, but the description earns above baseline by clarifying that 'period' accepts both quarter form (2026-Q3) and month form (2026-09) — the schema example only shows the quarter form. It also explains the meaning of omitting the parameter entirely. bolag_id is left to the schema, which documents it adequately.

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 resource (moms/momsperioder) and precisely describes two distinct modes: a list of VAT periods with amounts, status and due date, or a VAT report with the boxes and amount payable. An agent can tell exactly what comes back in each case. It stops short of 5 because it never contrasts itself with adjacent sibling tools such as bokslut_och_deklaration or resultatrakning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditional guidance: omit period to list periods, supply a period to get the report. That is a clear when-to-use rule for the tool's two modes. There is no guidance on when to prefer a different sibling tool, so it is not a full 5.

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.