Skip to main content
Glama
hermoso-ai

Hermoso

Official

Upgrade plan

upgrade_plan
Read-only

List available plans and manage plan changes. New subscribers receive a Stripe checkout URL; existing plan changes or downgrades require action in app billing. Members see an 'ask admin' message.

Instructions

Change this account's SUBSCRIPTION plan (admin only). Call with no argument to list the plans (id · monthly price · monthly credits); call again with plan set to a plan id. A NEW subscriber gets a ready-to-pay Stripe Checkout URL to hand your human — THEY pay on Stripe (agents never spend money directly). If the account already has a paid plan, or you're DOWNGRADING, the change is made by a person in the app (Settings → Billing) and the tool returns exactly what to do. Members (read-only billing) get an honest 'ask an admin' message. Nothing is charged until your human pays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNothe plan id to move to (e.g. pro) — omit to list the available plans first
periodNobilling cadence — monthly (default) or yearly (2 months free)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNothe ready-to-pay Stripe Checkout URL (checkout mode)
modeNo'checkout' (a Stripe URL was minted) or 'in_app' (a person makes the change in the app)
planNothe target plan id
plansNoavailable paid plans ({id, name, priceUsd, credits}) when listing
actionNothe in-app action required ('upgrade' or 'downgrade')
periodNobilling cadence of the link — 'mo' or 'yr'
guidanceNoexact instructions when the change must be made in the app
chargeUsdNothe actual charge amount (yearly billing charges the annual total)
planLabelNothe target plan display name
monthlyUsdNothe plan’s monthly price in USD
Behavior5/5

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

Discloses that the tool itself does not charge—it returns a Stripe URL or instructions—aligning with the 'readOnlyHint' annotation. Adds important context (admin-only, no direct spending by agents, member limitation) beyond the annotation.

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 description is slightly verbose but well-structured, front-loading the core action. Every sentence adds unique value, though a minor trim could improve conciseness.

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?

Covers all behavioral nuances (new subscriber vs existing, downgrade, member limitation) and specifies return types (URL, instructions, message). Given the presence of an output schema, the description is complete without needing to detail return values.

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

Parameters5/5

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

The schema already provides descriptions for both parameters (plan, period) with 100% coverage. The description adds value by explaining the two-step workflow, plan id usage, and default period, making the parameters' semantics fully clear.

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 changes subscription plans, lists available plans, and handles different account states (new vs existing subscriber, admin vs member). It distinguishes its billing function from sibling tools like 'buy_credits' and 'billing_status'.

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?

Explicitly instructs to call with no argument to list plans, then with 'plan' set to an id. Provides guidance for accounts with existing paid plans or downgrades (direct user to app), and tells admins vs members what to expect.

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/hermoso-ai/hermoso'

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