Skip to main content
Glama
remoet-labs

remoet

Official
by remoet-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Get Upgrade Link

get_upgrade_link

Retrieve a Stripe Checkout URL to upgrade your Remoet subscription. Supports plan upgrades: free to pro, free to max, or pro to max.

Instructions

Get a Stripe Checkout URL the user can open to upgrade their subscription. This tool does NOT charge the user — it only returns a link; payment happens in the browser when the user completes Stripe Checkout. Present the "checkoutUrl" as a clickable link. Supports upgrades only: free→pro, free→max, pro→max. For downgrades or cancellation, direct the user to https://www.remoet.dev/settings.

Confirm with the user before calling this. Note: for a user who already has a paid subscription, changing tier (pro→max) may apply IMMEDIATELY with prorated billing against their existing payment method (response "message" instead of "checkoutUrl") — i.e. it can charge without a checkout step, so get explicit confirmation first. free→paid always returns a checkoutUrl (no charge until the user completes Stripe Checkout).

This tool is environment-aware. The response includes an "environment" field (local | stage | production). Only "production" charges real money — local and stage run Stripe in test mode (the response includes a sandboxNote field with test-card instructions). Always tell the user which environment they're entering before they click through.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYesThe plan to upgrade to
confirmNoSet true ONLY after the user has explicitly agreed. Required for an immediate pro→max upgrade (charges the existing card right away). Not needed for free→paid, which returns a checkout link and charges nothing until the user completes Stripe Checkout.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Description discloses that it does not charge the user directly, explains pro→max may apply immediately with prorated billing, and details environment awareness (local/stage/production) including sandbox mode. No contradiction with annotations (readOnlyHint=false is consistent with creation of a link).

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?

Description is longer but each sentence is purposeful. Front-loaded with main purpose and key facts. Could be slightly more concise, but no extraneous information.

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?

Despite no output schema, description explains return fields (checkoutUrl, message, environment, sandboxNote) and how to present them. Covers all necessary information for an agent to use the tool correctly.

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?

Schema coverage is 100%, but description adds nuance: explains plan enum in context of upgrade paths, and clarifies confirm parameter's conditional necessity (immediate charge vs. checkout URL). Adds meaningful value beyond 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?

Clearly states it returns a Stripe Checkout URL for upgrading subscriptions, specifies upgrade paths (free→pro, free→max, pro→max), and distinguishes from downgrades/cancellation. Verb+resource is explicit.

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?

Provides explicit when-to-use (upgrades only) and when-not-to (downgrades/cancellation, directing to another URL). Also instructs to confirm with user and warns about immediate charging for pro→max. No sibling overlap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/remoet-labs/remoet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server