Skip to main content
Glama

Vinka

Boka möte med Vinka

boka_mote
Read-onlyIdempotent

Ger länken för att boka 20 minuter på video med en redovisningskonsult på Vinka, för den som vill lämna över bokföringen eller byta byrå.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 genuinely useful context beyond that: the tool only hands back a link rather than performing a booking or contacting anyone, which clarifies the side-effect profile. It does not say whether the link expires or is per-session.

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?

A single sentence with the deliverable ('Ger länken') front-loaded, followed by the qualifying audience. No filler and no repetition of the title.

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 zero-parameter tool with no output schema, the description covers what the agent needs: what it returns (a link), what the link is for, and who should use it. Only minor details such as link lifetime or required context are absent.

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, so there is nothing for the description to disambiguate; baseline is 4. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific outcome — 'Ger länken för att boka 20 minuter på video med en redovisningskonsult på Vinka' — naming the exact resource (a booking link), duration (20 min), format (video) and counterpart (accounting consultant). This is clearly distinguishable from data-retrieval siblings such as huvudbok or kundfordringar.

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?

Adds a usage condition: for users who want to hand over their bookkeeping or switch accounting firms. That tells the agent when the tool is relevant, but there are no explicit exclusions or pointers to alternative siblings for adjacent needs.

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.