Skip to main content
Glama

Vinka

Ett verifikat

hamta_verifikat
Read-onlyIdempotent

Hämtar ett verifikat med alla rader och vilka underlag som är kopplade.

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": {
      "verifikat_id": "<verifikat_id>"
    },
    "name": "hamta_verifikat"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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. The description adds genuine value by disclosing the shape of the payload (all rows and linked underlag), but says nothing about behavior when the id does not exist or about company-scoping side effects.

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?

One compact sentence, front-loaded with the verb and resource, with no filler. It is perhaps slightly over-terse given that the key input (where the id comes from) is never addressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return-value burden; it does so only at a high level (rows + linked underlag) without field detail or ordering. For a two-parameter lookup with strong annotations this is adequate but leaves the identifier's provenance and error behavior unaddressed.

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 50%: bolag_id is documented in the schema as coming from lista_bolag and only needed with multiple companies, while verifikat_id has no schema description. The description does not compensate by explaining that verifikat_id is the voucher number obtained from lista_verifikat, so the undocumented half remains unexplained.

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?

"Hämtar ett verifikat" gives a specific verb and resource, and the trailing clause clarifies that the result includes all posting rows plus linked supporting documents (underlag) — more than a bare restatement of the title. It does not explicitly contrast with the sibling lista_verifikat, so the singular-fetch vs. list distinction must be inferred from the name and the required verifikat_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no mention of when to prefer lista_verifikat to locate an id, and no stated prerequisites or failure conditions (e.g., unknown verifikat_id). Usage is only implied by the required identifier parameter.

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.