Skip to main content
Glama

Vinka

Obetalda kundfakturor

kundfordringar
Read-onlyIdempotent

Vilka kunder som är skyldiga bolaget pengar och hur mycket som har förfallit.

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

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

C2.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 the safety profile is fully covered by structured data. The description adds only a hint about scope ('förfallit' suggests overdue amounts), but it is ambiguous whether this covers all outstanding invoices, only overdue ones, or partially paid ones, and it says nothing about freshness or aggregation level.

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 short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than being purely economical.

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?

This is a simple read-only tool with one optional parameter and no output schema, so the description should carry the burden of explaining the returned content. It conveys the gist (owing customers plus overdue amount) but leaves open the granularity, whether invoice-level detail or dates are included, and how overdue is defined.

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 already explained in the schema (id from lista_bolag, only needed with multiple companies). The description adds no additional meaning about this 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.

Purpose3/5

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

The sentence identifies the resource precisely enough (customers who owe the company money and how much is overdue), so an agent can guess this is an accounts-receivable query. But it is framed as a statement of content rather than a verb+resource action, and it never distinguishes itself from the very similar sibling leverantorsfakturor (supplier invoices), which is the most likely confusion point.

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 when-to-use or when-not guidance at all. Nothing tells the agent to pick this over leverantorsfakturor, huvudbok, or balansrakning, and no prerequisites (e.g. needing a bolag_id when multiple companies exist) are mentioned in the description.

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.