Skip to main content
Glama

Upgrade or change plan

spur_change_plan
Destructive

Moves the user to another Spur plan (ids from spur_show_billing_options; usually team or brokerage).

  • No paid subscription yet: returns a Stripe checkout link. No confirmation needed.

  • Already subscribed: switches the plan immediately and charges or credits the prorated difference to the saved card. Call once without confirm to get the exact change, ask the user to approve it, then call again with confirm=true.

  • Moving to the Free plan returns a billing-portal link where the user cancels the paid subscription.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "spur_change_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoOnly for users who already have a paid subscription: true ONLY after they approved the switch and the prorated charge in the conversation.
plan_idYesTarget plan id, e.g. team or brokerage
action_tierNoMonthly Actions from the plan catalog; omit to preserve the current tier on the same plan
billing_intervalNoOmit to preserve the current interval for this plan
data_credit_tierNoMonthly Data Credits from the plan catalog; omit to preserve the current tier on the same plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / action_tier
      Added value: +{
      +  "description": "Monthly Actions from the plan catalog; omit to preserve the current tier on the same plan",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • removedInput schema / properties / billing_interval / default
      Removed value: -"monthly"
    • changedInput schema / properties / billing_interval / description
      Previous value: -"annual is cheaper per month"New value: +"Omit to preserve the current interval for this plan"
    • addedInput schema / properties / data_credit_tier
      Added value: +{
      +  "description": "Monthly Data Credits from the plan catalog; omit to preserve the current tier on the same plan",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • changedInput schema / properties / plan_id / description
      Previous value: -"Target plan id, e.g. agent, team, brokerage"New value: +"Target plan id, e.g. team or brokerage"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations disclose destructiveHint=true and non-idempotency, but the description adds the crucial context they don't: that an immediate switch charges or credits a prorated difference to the saved card, that the first call is a preview and the second with confirm=true executes it, and that different branches return different link types. This is exactly the money-moving behavior an agent must warn the user about.

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 front-loaded lines, each a distinct branch with its return value and required action; zero filler. The most consequential fact (prorated charge) sits in the branch an agent will hit most often.

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 five-parameter, destructive, open-world mutation with no output schema, the description covers what each branch returns (checkout link, immediate switch plus prorated charge, billing-portal link) and the required human-approval gate. Nothing an agent needs to invoke it safely is missing.

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 the baseline is 3, but the description adds meaning the schema cannot: confirm is framed as part of a two-call approval workflow rather than a bare boolean, and plan_id is anchored to the catalog returned by spur_show_billing_options. The tier parameters (action_tier, data_credit_tier, billing_interval) are left to the schema, which documents them adequately.

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 and resource ('Moves the user to another Spur plan') and immediately names the sibling that supplies plan ids (spur_show_billing_options), plus examples ('team or brokerage'). An agent can distinguish this from credit-pack or phone-number purchase tools without opening any schema.

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 three explicit branches keyed to user state: no paid subscription (returns Stripe checkout, no confirmation), already subscribed (two-step call-then-confirm flow), and moving to Free (returns billing-portal link). It names the prerequisite source of plan ids and spells out the approval sequence, leaving nothing to inference.

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