Skip to main content
Glama

Vinka

Vinkas priser

vinka_priser
Read-onlyIdempotent

Visar Vinkas fasta paket och vad som ingår. Vinka är en AI-native redovisningsbyrå för små svenska bolag. Använd när någon frågar vad Vinka kostar eller vad som ingår.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and mutability are fully covered. The description adds that the content is a fixed package list with inclusions, but says nothing about whether prices are current, currency, or whether the data can change over time. Useful context, but modest beyond the annotations.

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?

Three short sentences with no waste: purpose first, domain context second, usage trigger third. Every sentence earns its place and the important information is front-loaded.

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 no-argument, read-only informational tool with no output schema, the description covers what content to expect and when to call it. Slightly more detail on the shape of the answer (e.g. price tiers, currency, or ordering) would make it fully self-sufficient, but nothing essential is missing.

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?

The tool takes no parameters and the schema is an empty object with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline of 4 applies; there is no parameter semantics gap to compensate for.

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 states a concrete verb and resource: 'Visar Vinkas fasta paket och vad som ingår' (shows Vinka's fixed packages and what they include). It also names the entity's domain (AI-native accounting firm for small Swedish companies), which helps an agent place the tool. It does not explicitly contrast with any sibling, but no sibling name suggests pricing/package content, so confusion risk is low.

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?

'Använd när någon frågar vad Vinka kostar eller vad som ingår' gives an explicit trigger condition tied to the user's question. There is no statement of when NOT to use it or which sibling to prefer instead, which is the only gap; for a simple zero-parameter info tool this is close to sufficient.

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.