Skip to main content
Glama

upgrade

Get a link to upgrade the account to Pro (raises the monthly quota).

    Returns a Stripe Checkout URL for the human to open and pay — no pingwa
    password needed, the card is handled by Stripe. If the account is already
    on a paid plan, returns a billing-portal URL to switch tier, change Team
    seats or cancel instead. Also lists every way forward with its price,
    cheapest first: a one-time message pack for a low-volume number, Team
    seats, the next plan.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real context: no pingwa password is needed, Stripe handles the card, and behavior diverges based on account state (checkout URL vs. billing-portal URL). It omits whether calling it has any side effect on the account, any rate limits, or the URL's lifetime/expiry, which are meaningful gaps for a billing-related 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?

The core action and return are front-loaded in the first sentence, with the conditional branch second. The final sentence listing all pricing options is somewhat sprawling and partially duplicates what the output schema presumably conveys, but nothing is truly wasted.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains the two URL variants helpfully. Given zero parameters and no annotations, the only remaining shortfall is the absence of any note on side effects or link lifetime.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to add beyond the empty schema. The description correctly does not invent parameters.

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 ('Get a link to upgrade the account to Pro') and immediately names the effect ('raises the monthly quota'). It is unmistakably distinct from siblings like ask, notify, or schedule, which are unrelated workflows.

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

Usage Guidelines4/5

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

Implies the triggering condition (user wants to upgrade or raise quota) and explains the branch for accounts already on a paid plan, which redirects to a billing portal instead. It does not explicitly name exclusions or sibling alternatives, but none of the siblings overlap in purpose, so the context is sufficient.

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.