Skip to main content
Glama

Vinka

Löner

lon
Read-onlyIdempotent

Lönekörningar för ett år, valfritt en månad: bruttolön, skatt, arbetsgivaravgift och nettolön per anställd. Personnummer och bankkonton visas aldrig.

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

Input Schema

NameRequiredDescriptionDefault
arNo
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
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds genuine behavior beyond them: the exact figures returned and the privacy guarantee that personal identity numbers and bank accounts are never exposed — material context for deciding whether the output is safe to surface.

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 tight sentences: the core operation and scope first, the privacy caveat second. Nothing is redundant and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with no output schema, the description covers what is returned and the privacy constraint. It omits what happens when the optional ar is omitted (default year?) and whether results are aggregated per year or listed per payroll run, which an agent needs before calling.

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 only 33%, with bolag_id the sole documented parameter. The description partially compensates by mapping to the two undocumented ones — "ett år" for ar and "valfritt en månad" for manad — but adds no format, default-year, or interaction detail, leaving the compensation incomplete.

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+resource ("Lönekörningar för ett år") and enumerates the returned figures: gross pay, tax, employer contributions, net pay per employee. That is far more specific than the name alone, though it never names a sibling tool to contrast with (e.g. huvudbok 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 Guidelines3/5

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

"för ett år, valfritt en månad" implies the year-wide vs. single-month usage pattern, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative. An agent can infer the scoping from the phrasing but gets no routing guidance.

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.