Skip to main content
Glama

Vinka

Vad Vinka väntar på

vantar_pa_mig
Read-onlyIdempotent

Listar vad Vinka har bett dig om och som inte är klart: saknade kvitton, kontoutdrag eller svar, med 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": "vantar_pa_mig"
  }
}

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds real value by naming what the list contains (unfinished requests, deadlines), but it does not say whether items disappear once answered, how they are ordered, or whether the list is scoped to one 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?

A single front-loaded sentence with the payload (what is listed, with examples, plus deadline) stated immediately. The colon-joined phrasing is slightly compressed but no sentence is wasted.

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 simple, optional-parameter, read-only list tool with no output schema and full parameter documentation, the description supplies enough to call it correctly. Only minor gaps (ordering, whether answered items are removed) remain.

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 description coverage is 100% and the single optional bolag_id is fully explained in the schema itself ('Bolagets id från lista_bolag...'). The description adds nothing about the parameter, so the baseline of 3 applies.

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?

Uses a specific verb ('Listar') plus a clearly bounded resource: outstanding items Vinka has asked the user for. It enumerates the concrete categories (missing receipts, account statements, replies) and notes that a deadline is included, which lets an agent tell this apart from general message or ledger tools without opening the schema.

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 content — an agent would reach for this when checking what is still owed to Vinka — but there is no explicit when-to-use statement, no exclusions, and no named alternative such as las_meddelanden or skicka_underlag for the adjacent tasks.

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.