Skip to main content
Glama
Sign In
garu-mcp

garu-mcp

Official
by Garu-Pagamentos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_scheduled_charge_payment_method

Update the saved payment method for a recurring series. The new method must belong to the same customer and applies to future charges.

Instructions

Swap the saved card on a recurring series. The new PaymentMethod must belong to the same customerId. Future cycles silent-charge the new card; the in-flight cycle is not retroactively rebound.

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": {
      "id": "<id>",
      "paymentMethodId": "<paymentMethodId>"
    },
    "name": "change_scheduled_charge_payment_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesScheduled charge ID
paymentMethodIdYesPaymentMethod id to bind. Must belong to the same customerId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: it describes the swap action, the customerId constraint, and the differential treatment of future vs. in-flight cycles entirely. No contradictions present.

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?

The description is two sentences long, front-loaded with the primary action, and every sentence adds value. No unnecessary words or repetition.

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 tool with two parameters and no output schema, the description fully covers what the tool does, its constraints, and its effect on different cycles. No gaps are evident.

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?

The description adds meaning beyond the input schema by explaining the overall action ('swap') and the behavioral effects on future and current cycles. While the schema covers the parameters adequately, the description provides context that is not present in 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?

The description explicitly states 'Swap the saved card on a recurring series', using a specific verb and resource that clearly distinguishes it from sibling tools like 'clear_scheduled_charge_payment_method' which removes the payment method.

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?

The description provides clear context on when to use the tool by specifying constraints ('must belong to the same customerId') and behavioral effects on future and in-flight cycles. However, it does not explicitly contrast with alternative sibling tools.

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