Skip to main content
Glama
Sign In
garu-mcp

garu-mcp

Official
by Garu-Pagamentos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clear_scheduled_charge_payment_method

Removes saved card from a recurring series. Future payments use email-with-link for card entry or alternative methods.

Instructions

Clear the saved card on a recurring series. Future cycles fall back to the email-with-link flow so the customer can re-enter card details or pay via PIX/Boleto.

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>"
    },
    "name": "clear_scheduled_charge_payment_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesScheduled charge ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It discloses a key behavioral effect (future cycles fall back to email-link flow), but omits expected side effects, permission requirements, or reversibility. Reasonable but not exhaustive.

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?

Two concise sentences, no wasted words. The core action and consequence are presented upfront. Ideal length for a simple tool.

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

Completeness3/5

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

Given no output schema and simple input, the description adequately explains the tool's purpose and fallout. However, it lacks detail on response format or error handling, which would be expected for a mutation tool.

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?

With 100% schema coverage, the description adds no further detail about the 'id' parameter beyond what the schema already provides. It correctly implies which entity is affected but does not enrich parameter semantics.

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 clearly states the verb 'clear' and the resource 'saved card on a recurring series'. It distinguishes from sibling tools like 'change_scheduled_charge_payment_method' by focusing on removal vs modification.

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?

The description implies usage for removing a saved card to allow fallback flows, but does not explicitly state when to use vs alternatives (e.g., 'change_scheduled_charge_payment_method'), nor does it mention prerequisites or contraindications.

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