Skip to main content
Glama

stripe_set_payment_method

Enable or disable a specific payment method in a Stripe payment method configuration to control checkout display; requires confirmation and is audit-logged.

Instructions

Turn one payment method of a Stripe payment method configuration on or off (display preference). The method must exist in that configuration (see stripe_list_payment_method_configs). Needs confirm:true; audit-logged.

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": {
      "site": "<site>",
      "config_id": "<config_id>",
      "method": "<method>",
      "enabled": "<enabled>",
      "confirm": "<confirm>"
    },
    "name": "stripe_set_payment_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
methodYesPayment method key, e.g. card, klarna, sofort
confirmYesMust be true: this changes the live Stripe account
enabledYestrue = on, false = off
config_idYesPayment method configuration id (pmc_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the confirm:true gate, that the action is audit-logged, and that the change is a display preference on the live account. It does not state reversibility or the response/error behavior, which is a modest remaining gap for a mutation tool.

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?

Three short sentences, front-loaded with the operation, then the precondition, then the confirmation requirement. No filler and nothing buried.

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 5-required-param mutation tool with no annotations and no output schema, the description covers effect, prerequisite, confirmation, and audit logging. What is missing is only peripheral: what an agent should expect on failure or when the method is absent from the configuration.

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 a 3 is the baseline, but the description adds real meaning: it defines 'enabled' as a display preference rather than actual payment capability, restates the confirm gate, and points to the sibling tool that supplies config_id/method. That goes beyond restating the schema.

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 (turn on/off) on a specific resource (one payment method within a Stripe payment method configuration) and clarifies the effect is a display preference rather than payment enablement. That qualifier alone lets an agent distinguish this from generic Stripe settings tools.

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 a clear precondition (the method must already exist in that configuration) and routes the agent to stripe_list_payment_method_configs for discovery. It stops short of an explicit when-not-to-use or a named alternative for the actual capability toggle, so it is strong but not exhaustive.

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