Skip to main content
Glama

update_plan_limits

DestructiveIdempotent

Change the usage limits on an app's existing tiers (e.g. set ai_generations_daily to 200 on pro). WRITE, human-gated: a real write requires an elicitation-capable client; the human sees the per-tier before -> after diff and must click approve. 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. Tier-keyed, so one call can set a new limit key across every tier in a single atomic write. Use -1 for unlimited, matching the catalog convention. This writes ONLY the limits object: it never touches Stripe, prices, or plan names, so it cannot mint a price by accident. Changing prices or adding a tier is a different job: use create_app_kit or the dashboard. Set dry_run to preview the before/after without writing. After this succeeds, run bun run plans:sync in the app repo and commit the regenerated plans.json so the code and the catalog agree.

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_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomerge
app_idYes
dry_runNo
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/idempotent, but the description adds substantial behavior beyond them: a human-gated approval flow with a per-tier before -> after diff, refusal semantics for non-elicitation clients, atomic multi-tier writes, and the -1 unlimited convention. It also disclaims side effects outside the limits object, which is the key risk signal for a destructive tool.

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 purpose, then safety gating, then scope boundaries, then the post-write sync step — a sensible order with no filler sentences. The middle paragraph is dense and packs several distinct rules into one block, which slightly hurts scanability.

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

Completeness4/5

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

For a destructive, no-output-schema write with a nested parameter object, the description covers prerequisites, approval mechanics, scope limits, preview, and the follow-up required to keep code and catalog in sync. Only the merge-vs-replace behavior of `mode` is left entirely to an undescribed enum default.

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?

With 0% schema description coverage and a nested object parameter, the description does most of the work: it explains the tier -> limit-key -> number shape by example, the -1 sentinel, and dry_run's preview behavior. The gap is `mode` (merge vs replace), which is never mentioned despite materially changing what the write does to existing limits.

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 precise verb and resource ('Change the usage limits on an app's existing tiers') with a concrete example ('set ai_generations_daily to 200 on pro'), and explicitly bounds scope against neighboring operations: 'never touches Stripe, prices, or plan names.' It routes price/tier-creation work elsewhere, so an agent can separate it from update_plan_pricing or create_app_kit without opening schemas.

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 explicit when-to-use, when-refused conditions (elicitation-capable client required), the documented escape hatch (SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 plus confirm_write:true), what to do instead for adjacent jobs (create_app_kit or dashboard for prices/new tiers), and the required follow-up step (bun run plans:sync and commit).

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