Skip to main content
Glama

Car Background AI

Change subscription plan

change_plan
Destructive

Change the plan of a workspace that already has a subscription, to a price_id from list_plans. Always call it first with confirm: false, which for an upgrade returns a preview of the prorated charge and charges nothing, and get the user's agreement to that amount. With confirm: true an upgrade charges the payment method on file immediately and adds the photos at once, while a smaller plan charges nothing now and is booked to start at the next renewal. For a workspace without a subscription it returns no_active_subscription; use create_checkout there instead. It cannot cancel a subscription; the user does that in the app. Needs an OAuth sign-in: with an API key it returns an error pointing to the app.

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": {
      "price_id": "<price_id>",
      "confirm": "<confirm>"
    },
    "name": "change_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesfalse previews an upgrade; true applies the change.
price_idYesA `price_id` from list_plans.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial context beyond the destructiveHint=true annotation: `confirm: false` charges nothing and previews the prorated amount, `confirm: true` on an upgrade charges the payment method on file immediately, a downgrade charges nothing now and is booked for next renewal, and OAuth is required (API keys get an error). The only gap is that it doesn't say whether a plan change is reversible or how to undo a mistaken confirmation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and then sequenced as preview → confirm → edge cases → auth, so the agent reads the critical instruction first. It is dense but nearly every clause carries distinct operational information; the proration sentence is slightly long but earns its length.

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?

Covers everything an agent needs for a two-parameter mutation with no output schema: the required two-step confirmation flow, billing outcomes, the `no_active_subscription` return case, the alternative tool, an explicit exclusion (no cancellation), and the auth requirement.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning the schema does not: the consequence of each `confirm` value under upgrade versus downgrade scenarios, and the provenance/constraint of `price_id`. An agent knows exactly what the boolean does financially before calling.

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?

Opens with a specific verb and resource ('Change the plan of a workspace that already has a subscription') and immediately scopes the valid input to a `price_id` from list_plans. It clearly distinguishes itself from create_checkout (workspaces without a subscription) and from list_plans (the source of price IDs).

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?

Gives an explicit mandatory workflow: always call first with `confirm: false` and obtain the user's agreement to the previewed prorated amount. It names the alternative for the no-subscription case (create_checkout) and states an exclusion — cancellation must happen in the app, not through this tool.

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