Skip to main content
Glama
Sign In
Prufa

Prufa

Official
by prufa-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prufa_upgrade_plan

Subscribe or upgrade your workspace to a paid plan. Returns a Stripe checkout URL for a 7-day card-first trial. Idempotent for safe retries.

Instructions

Subscribe or upgrade this workspace to a paid plan (starter | pro | team). Returns a Stripe checkout_url the HUMAN opens in a browser to start the 7-day card-first trial — the agent never enters card details. Mutating + idempotent. [Pro]

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": {
      "tier": "<tier>"
    },
    "name": "prufa_upgrade_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYesTarget paid plan.
cancel_urlNoOptional URL Stripe redirects to on cancel.
success_urlNoOptional URL Stripe redirects to on success.
idempotency_keyNoOptional. Replays of the same key within 24h return the original response without re-executing — pass one to make retries safe. Omitted: a fresh key is generated, so each call executes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description bears full responsibility. It discloses that the tool is mutating and idempotent, describes the return value, and notes the agent's role restriction. However, it lacks details on side effects (e.g., what happens if already subscribed) or dependencies (e.g., workspace setup).

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?

The description is extremely concise: three sentences with no redundancy. Each sentence adds critical information: purpose, human action requirement, and behavioral characteristics (mutating, idempotent, trial).

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?

Given no output schema, the description adequately explains the return value ('Stripe checkout_url'). It covers the trial, idempotency, and agent limitation. It could mention error scenarios or prerequisites, but the tool is simple enough that this level of detail suffices.

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?

The input schema has 100% description coverage, so the baseline is 3. The description does not add meaningful parameter information beyond the schema; it only lists the tier options already in the enum. The idempotency_key behavior is already well-described in the schema.

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?

The description clearly states the tool's purpose: 'Subscribe or upgrade this workspace to a paid plan' and lists the specific tiers ('starter | pro | team'). It distinguishes itself from sibling billing tools like prufa_billing_portal (manage existing) and prufa_buy_credits (purchase credits) by focusing on plan subscription/upgrade.

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?

The description provides explicit guidance: the agent never enters card details and returns a Stripe checkout URL for the human to open. It describes the trial period and idempotency behavior. It could be improved by noting when not to use (e.g., if workspace already on a plan), but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools