Skip to main content
Glama
Sign In
klarna-mcp

klarna-mcp

by Walma-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get dispute

get_dispute
Read-onlyIdempotent

Retrieve a Klarna dispute by payment dispute ID to view its current status, requests, deadlines, and evidence history.

Instructions

Get one dispute in its current state, including its requests, deadlines and evidence history (Klarna Disputes API v4).

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": {
      "payment_dispute_id": "<payment_dispute_id>"
    },
    "name": "get_dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_dispute_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description earns credit by disclosing payload scope (requests, deadlines, evidence history) and freshness ("current state"), which matters because there is no output schema — though it omits auth or identifier-validity notes.

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 front-loaded sentence with no filler; the core action leads and the returned content follows. Every clause contributes.

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 simple single-item read with a full safety annotation set and no output schema, the description covers what is returned and the resources involved. The only notable gap is the absence of any identifier provenance or error behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter payment_dispute_id gets no explanation of format, source, or constraints. "One dispute" only weakly implies that an identifier must be supplied; the description adds essentially no meaning beyond the schema's property name and maxLength.

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 gives a specific verb and resource ("Get one dispute") and scopes the result to current state plus requests, deadlines and evidence history. A sibling list_disputes exists, and the singular "one dispute" implies retrieval by identifier versus listing, though the sibling is not named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: you fetch a single dispute when you have an identifier and need its detail. There is no explicit when-to-use statement, no prerequisites, and no pointer to list_disputes for discovery versus this tool for detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools