Skip to main content
Glama
mcp-server-vippsmobilepay

mcp-server-vippsmobilepay

Cancel Recurring charge (Vipps MobilePay)

vipps_cancel_charge
Destructive

Cancel a pending, due, reserved, or partially captured Recurring charge to release reserved funds back to the customer. Refuses other statuses; irreversible, so confirm each call.

Instructions

Cancel a pending, due, reserved or partially captured Recurring charge; money reserved and not captured is released to the customer. A pending, due or reserved charge ends as CANCELLED, a partially captured one as CHARGED. Reads the charge first and refuses any other status. The agreement itself is not changed. 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>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "vipps_cancel_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
chargeIdYesThe Recurring charge id, e.g. chr-123ab.
agreementIdYesThe Recurring agreement id, e.g. agr_5kSeqz.
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.3/5.0
Behavior5/5

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

Goes well beyond the supplied annotations: it discloses the terminal states (CANCELLED vs CHARGED for partially captured), that reserved-but-uncaptured money is released, that the agreement is untouched, that a pre-read guards against wrong statuses, that the action is irreversible, and that writes are gated behind a feature flag plus human confirmation. This is exactly the destructive, side-effecting context an agent needs before calling.

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 eligible statuses, then layers outcome, side effects, and gating in short clauses. Every sentence carries distinct information; none repeats the annotations or the schema.

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

Completeness5/5

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

For a destructive single-record mutation with no output schema, the description covers eligibility, result states, money movement, irreversibility, and the enablement/confirmation gates. Nothing material an agent would need before invoking it is missing.

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 100%, with each of the three parameters documented in the schema itself (charge id format, agreement id format, and how to use the idempotency key). The description adds no parameter-level detail, so the schema is doing the work and the baseline of 3 applies.

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?

States a specific verb and resource ('Cancel a ... Recurring charge') and enumerates the eligible statuses (pending, due, reserved, partially captured), which pins down the operation precisely. It stops short of naming a sibling such as vipps_refund_charge, so the agent must infer the refund-vs-cancel boundary from the captured-money wording rather than an explicit route.

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?

Gives clear context for use ('pending, due, reserved or partially captured') and, importantly, when NOT to use it: 'Reads the charge first and refuses any other status.' It also flags the operational prerequisites (disabled by default via VIPPS_ENABLE_WRITES / gateway host policy, human confirmation per call). No alternative tool is named for charges already fully captured, which keeps it from a 5.

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