Skip to main content
Glama

Vinka

Skriv till Vinka

skicka_meddelande

Skickar ett meddelande till din redovisningskonsult på Vinka, t.ex. en fråga eller information om en affär. Svaret läser du med las_meddelanden.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "meddelande": "<meddelande>"
    },
    "name": "skicka_meddelande"
  }
}

Input Schema

NameRequiredDescriptionDefault
bolag_idNoBolagets id från lista_bolag. Behövs bara om du har flera bolag hos Vinka.
meddelandeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is pre-supplied. The description adds genuine context beyond that — that the message goes to a human accounting consultant and that a reply is retrieved via las_meddelanden — but says nothing about delivery timing, whether a sent message can be edited or withdrawn, or any rate limits. Adequate, not rich.

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 short sentences with zero padding: purpose and recipient first, then the follow-up path. Every clause carries information the agent needs.

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 two-parameter, one-required message tool with no output schema, the definition covers what the tool does, who receives it, and how the interaction continues. The only omission is any reference to the optional bolag_id parameter and message length, which the schema handles itself.

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 50%: bolag_id carries its own description ("Behövs bara om du har flera bolag"), while meddelande has no schema description at all. The description partly compensates by characterizing the message content (a question or business information), but never mentions bolag_id or the 4000-character constraint, leaving the required parameter's semantics thin.

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 verb and resource ("Skickar ett meddelande") plus the recipient (the accounting consultant at Vinka), and explicitly names the sibling tool used for the counterpart operation (las_meddelanden). An agent can distinguish it from las_meddelanden and skicka_underlag without opening any schema.

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?

Gives concrete when-to-use context ("en fråga eller information om en affär") and routes the agent to las_meddelanden for reading the reply, which is the key usage boundary. It stops short of explicit when-not-to-use exclusions or prerequisites, so a 4 rather than a 5.

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.