Skip to main content
Glama

Patch MCP

execute_subscription_change

Destructive

Apply the exact, unexpired quote the user explicitly approved after seeing its immediate charges, recurring price, effective time and limits. May charge a saved payment method, change the subscription, cancel renewal or undo a scheduled change. Set user_authorized=true only after that approval; never infer permission to spend. Reuse the same request_id and arguments after a lost response. Return any payment/authentication URL for the user to complete; never collect payment credentials in chat.

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": {
      "quote_id": "<quote_id>",
      "user_authorized": "<user_authorized>",
      "request_id": "<request_id>"
    },
    "name": "execute_subscription_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYes
request_idYes
user_authorizedYesThe user explicitly approved this quote's charges and terms. Never infer approval from a request to preview.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / user_authorized
      Added value: +{
      +  "const": true,
      +  "description": "The user explicitly approved this quote's charges and terms. Never infer approval from a request to preview.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "quote_id",
      -  "request_id"
      -]New value: +[
      +  "quote_id",
      +  "user_authorized",
      +  "request_id"
      +]
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "propertyNames": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "error": {
      -        "type": "string"
      -      },
      -      "message": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "error"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "message": {
      -        "type": "string"
      -      },
      -      "next_action": {
      -        "type": "string"
      -      },
      -      "operation_id": {
      -        "type": "string"
      -      },
      -      "status": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "operation_id",
      -      "status"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "agent_payment_support": {
      +        "type": "string"
      +      },
      +      "next_action": {
      +        "const": "get_billing",
      +        "type": "string"
      +      },
      +      "operation_id": {
      +        "type": "string"
      +      },
      +      "payment_flow": {
      +        "const": "stripe_checkout",
      +        "type": "string"
      +      },
      +      "status": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "url",
      +      "next_action"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "error": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "error"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "message": {
      +        "type": "string"
      +      },
      +      "next_action": {
      +        "type": "string"
      +      },
      +      "operation_id": {
      +        "type": "string"
      +      },
      +      "status": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "operation_id",
      +      "status"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Beyond the `destructiveHint: true` annotation, the description adds critical operational behavior: it instructs the AI to reuse the `request_id` after a lost response and specifies the output must be a payment/authentication URL, preventing the AI from attempting to collect sensitive data in chat.

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?

Although long, the description is highly efficient and dense. Every sentence serves to define the scope, safety guardrails, or operational constraints, ensuring zero waste of words for this complex financial action.

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?

Given the high complexity and financial risk of the operation, the description is exhaustive. It covers what the tool does, when it can be used, safety protocols, and expected response types.

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

Parameters5/5

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

Given the low schema coverage (33%), the description is essential. It adds vital semantic meaning to the parameters: `quote_id` must be from an unexpired quote, and `user_authorized` means the user has actively consented to the financial terms.

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 identifies the resource ('quote') and the action ('Apply the exact, unexpired quote'), specifically stating it executes a subscription change. It implicitly differentiates itself from `preview_subscription_change` in the sibling list by focusing on execution versus previewing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit preconditions for use, such as the quote being 'unexpired' and the user having 'explicitly approved' it. It dictates when to use the parameter `user_authorized` (only after explicit approval).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources