Skip to main content
Glama
Sign In
klarna-mcp

klarna-mcp

by Walma-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get payout

get_payout
Read-onlyIdempotent

Retrieve a Klarna payout by its payment reference from your bank statement, returning all totals in minor units.

Instructions

Get one Klarna payout by its payment_reference (the reference on your bank statement), with all totals in minor units.

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_reference": "<payment_reference>"
    },
    "name": "get_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_referenceYesPayout reference, as shown on the bank statement or in list_payouts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond them — totals are in minor units — but says nothing about error behavior when the reference is unknown or about the response shape.

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?

One sentence, no filler, with the core action front-loaded and the identifier and unit convention appended as useful qualifiers. Nothing could be cut without losing meaning.

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 single-parameter read tool with no output schema, the description covers the identifier source and the currency-unit convention, which is the main non-obvious detail an agent needs. It stops short of describing what a returned payout contains, but the essentials are present.

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% for the single parameter, so the schema already explains payment_reference, including that it appears on the bank statement or in list_payouts. The description's parenthetical largely restates that, adding only slight reinforcement, so the baseline of 3 applies.

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 (get one Klarna payout), names the identifying key (payment_reference), and scopes it against the sibling list_payouts / get_payout_summary by making clear it retrieves a single payout. An agent can select it without opening the schema.

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 implied by the requirement of a bank-statement reference and the singular 'one payout', which distinguishes it from the list/summary siblings. However, there is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative.

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