Skip to main content
Glama

update_plan_pricing

Destructive

Change what an app's EXISTING tiers charge: the amount, the billing model (one_time vs subscription), or both. WRITE, human-gated at the highest tier: a real write requires an elicitation-capable client, and the human types the tier, billing model and price into a form. Those typed values OVERRIDE the arguments here, which only pre-fill the proposal, so the model cannot move a price on its own. Clients without elicitation are refused UNLESS the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and the call passes confirm_write:true, which is how Claude Code and cron reach these writes; dry_run still works anywhere. Stripe prices are immutable, so this mints a NEW price and repoints the plan; the old price object is left intact and existing subscribers keep the price they signed up on, so this changes what NEW buyers pay. Switching a tier to one_time also clears its monthly/yearly price ids, so checkout cannot fall back to a recurring price the pricing page no longer advertises. Free, contact and payg tiers are refused: converting those is a catalog change, not a reprice. Use list_plans first for tier slugs and current amounts, and run bun run plans:sync in the app repo afterwards to regenerate plans.json.

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": {
      "app_id": "<app_id>",
      "updates": "<updates>"
    },
    "name": "update_plan_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
dry_runNo
updatesYes

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?

The annotations only say write, destructive, non-idempotent, open-world; the description adds substantially more: a human-gated elicitation flow whose typed values override the arguments, an environment-variable escape hatch, and the fact that dry_run is always safe. It also discloses the downstream mechanics (a new Stripe price is minted, the old price object and existing subscribers are untouched, so only new buyers are affected) and the side effect of switching to one_time clearing recurring price ids. The one gap is that it references confirm_write:true, which does not appear in the input schema, leaving the agent unsure whether that parameter is accepted.

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?

The purpose sentence is front-loaded, and almost every clause adds operational value an agent could not infer elsewhere (gating, refusal cases, follow-up command). It is dense and long for a single tool, and the confirm_write reference inside the behavior paragraph is slightly buried, but there is little outright waste.

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 destructive, non-idempotent mutation with no output schema and zero schema coverage, the description covers the gating path, the credentialless fallback, the refusal surface, the irreversible-but-non-disruptive pricing model, and the required post-call sync. An agent has enough to decide whether it can call this at all and what will happen if it does.

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 description coverage is 0%, so the description carries the full burden, and it does: it names the amount and billing model (one_time vs subscription) semantics of the updates array, points to list_plans for valid tier slugs, explains that dry_run works in any client, and describes the monthly/yearly price id consequence. The only shortfall is that the undocumented confirm_write flag it mentions is absent from the schema, which slightly muddies rather than clarifies the parameter set.

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 with explicit scope: it changes what an app's EXISTING tiers charge (amount, billing model, or both). It also carves out what it does not do (free/contact/payg tiers are refused, catalog changes belong elsewhere), which separates it from siblings like update_plan_limits and update_plan_meta.

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 prerequisite (use list_plans first for tier slugs and current amounts), an explicit follow-up (`bun run plans:sync` to regenerate plans.json), and explicit routing for the alternative path (non-elicitation clients need the env flag plus confirm_write:true; dry_run works anywhere). Nothing about when to reach for this tool is left 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