Skip to main content
Glama
mcp-server-vippsmobilepay

mcp-server-vippsmobilepay

Refund Recurring charge (Vipps MobilePay)

vipps_refund_charge
Destructive

Refund all or part of a charged Recurring payment to a customer. Validates the charge amount and currency before sending the refund to Vipps MobilePay; refunds cannot be undone.

Instructions

Refund all or part of a charged Recurring charge to the customer. Reads the charge first and refuses, without sending anything, when the currency differs or the amount is more than is charged and not yet refunded. The description is sent to Vipps MobilePay and is not logged. Moves or releases money and cannot be undone. Disabled by default (VIPPS_ENABLE_WRITES, or the gateway host policy enableWrites); a person should confirm every call.

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": {
      "agreementId": "<agreementId>",
      "chargeId": "<chargeId>",
      "amount": "<amount>",
      "currency": "<currency>",
      "description": "<description>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "vipps_refund_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount in minor units (øre, cent): 125.50 kr is 12550.
chargeIdYesThe Recurring charge id, e.g. chr-123ab.
currencyYesISO 4217 currency code of the payment.
agreementIdYesThe Recurring agreement id, e.g. agr_5kSeqz.
descriptionYesWhy the charge is refunded (1-100 characters), as Vipps MobilePay requires.
idempotencyKeyYesRequired operation key (8-40 letters, digits or dashes), sent as Idempotency-Key. Choose a new one for each new change, record it before the call, and send the same key when repeating that change after a failure or a lost answer: Vipps MobilePay then carries it out only once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: it reads the charge first, refuses without sending anything on currency mismatch or over-refund, moves money irreversibly, and requires enablement plus human confirmation. It also discloses that the refund description is sent to Vipps MobilePay and is not logged.

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?

Front-loads the action and then layers validation, safety, and enablement details in a compact sequence. Every sentence carries operational value for a destructive money-movement tool.

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?

Covers the critical context for a destructive refund: validation, irreversible side effect, enablement, and human confirmation. It could mention the success response shape, but no output schema exists and the invocation guidance is otherwise complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning: currency must match the charge and amount cannot exceed the charged-but-unrefunded balance. It does not add detail for every parameter, but the added validation rules are useful.

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: refund all or part of a charged Recurring charge. The 'Recurring charge' wording separates it from payment-refund siblings such as vipps_refund_payment.

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?

Explains the core use case and key prerequisites: it is disabled by default and requires human confirmation for every call. It also gives refusal conditions, but does not explicitly name when to choose a sibling like vipps_cancel_charge instead.

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