Skip to main content
Glama

Vinka

Läget i bolaget

hamta_status
Read-onlyIdempotent

Ger en lägesbild: resultat per månad i år, vad som ska göras nu, momsperioder med förfallodatum och hur många förfrågningar från Vinka som väntar på dig. Använd för frågor som 'hur ligger vi till?'.

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

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description's real contribution is telling the agent what surfaces in the response (monthly results, outstanding tasks, VAT due dates, pending request count) — valuable since there is no output schema — but it says nothing about time windows, pagination, caching, or whether the overview is scoped to a single company.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the payload enumeration is front-loaded and the usage cue is compressed into one short clause. Dense and waste-free, though the colon-separated list of four items reads a bit like raw enumeration rather than prioritized information.

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 aggregate/dashboard tool with one optional parameter and no output schema, the enumeration of returned content is the key thing an agent needs and it is present. Minor gaps remain around scope (per company vs. all) and whether the figures are live or snapshot, but the definition is adequate for correct invocation.

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 100% and the single optional bolag_id is well documented there ("Behövs bara om du har flera bolag"). The description adds nothing about this parameter, so the baseline of 3 applies — the schema does the work and the prose neither compensates nor misleads.

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 ("Ger en lägesbild") and then enumerates the actual contents: monthly result for the year, current to-dos, VAT periods with due dates, and the count of pending Vinka requests. This lets an agent distinguish it from narrower siblings like resultatrakning, moms or vantar_pa_mig without opening a schema, though those siblings are never named.

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?

Explicitly frames the use case with a natural-language trigger: "Använd för frågor som 'hur ligger vi till?'", i.e. broad status questions. It gives no when-not guidance or named alternatives for drilling into a single area (e.g. VAT details or individual requests), so it stops short of full 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.