Skip to main content
Glama

Confirm Plan Tier Change

confirm_plan_tier_change

Confirm a signed plan tier change. Requires confirm set to CONFIRM_TIER_CHANGE.

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": {
      "signupToken": "<signupToken>",
      "confirmType": "<confirmType>"
    },
    "name": "confirm_plan_tier_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
metadataNoAdditional template settings.
confirmTypeYesType of plan tier change being confirmed.
signupTokenYesSignup token returned by the preceding step of this flow.
paymentMethodIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / confirmType / description
      Added value: +"Type of plan tier change being confirmed."
    • addedInput schema / properties / metadata / description
      Added value: +"Additional template settings."
    • addedInput schema / properties / signupToken / description
      Added value: +"Signup token returned by the preceding step of this flow."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's job is to add flow context, which it does by marking this as the confirmation half of a signed-change flow. It also supplies the exact confirmation literal, which the schema does not (the schema's example is a generic "DELETE"). It omits whether the confirmed tier change can be undone or what state results after confirmation.

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?

Two short sentences, front-loaded with the action and followed by the blocking prerequisite. No filler and nothing that repeats structured fields verbatim.

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

Completeness3/5

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

For a consequential write that advances a plan tier change, the definition is thin: it never says the change becomes effective, whether it is reversible, or that it must follow change_plan_tier/prepare_plan_payment. The annotations and schema absorb the mechanical questions, but the workflow and consequence context an agent needs for a confirmation step is only partially present.

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

Parameters3/5

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

Schema coverage is 80%, so the schema already documents confirm, signupToken, confirmType and metadata; the baseline of 3 applies. The description does add real value by naming the literal value CONFIRM_TIER_CHANGE, which conflicts with the schema's misleading "DELETE" example, but it says nothing about confirmType values or what to do with paymentMethodId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Confirm a signed plan tier change" gives a specific verb (confirm) and resource (plan tier change), and the word "signed" implies it acts on a prepared change rather than initiating one. It stops short of explicitly distinguishing itself from siblings like change_plan_tier or confirm_plan_payment, so the agent has to infer the ordering.

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

Usage Guidelines3/5

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

The second sentence establishes a hard prerequisite (confirm = CONFIRM_TIER_CHANGE), which is genuine invocation guidance. However, there is no statement of when this should be used versus change_plan_tier or confirm_plan_payment, nor any note that it belongs at the end of a flow whose earlier step produced signupToken.

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