Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Upgrade plan

upgrade_plan

Switch subscription plans: list available plans, generate Stripe Checkout for new subscribers, or receive step-by-step instructions for upgrades and downgrades.

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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "action": {
-      "description": "the in-app action required ('upgrade' or 'downgrade')",
-      "type": "string"
-    },
-    "chargeUsd": {
-      "description": "the actual charge amount (yearly billing charges the annual total)",
-      "type": "number"
-    },
-    "guidance": {
-      "description": "exact instructions when the change must be made in the app",
-      "type": "string"
-    },
-    "mode": {
-      "description": "'checkout' (a Stripe URL was minted) or 'in_app' (a person makes the change in the app)",
-      "type": "string"
-    },
-    "monthlyUsd": {
-      "description": "the plan’s monthly price in USD",
-      "type": "number"
-    },
-    "period": {
-      "description": "billing cadence of the link — 'mo' or 'yr'",
-      "type": "string"
-    },
-    "plan": {
-      "description": "the target plan id",
-      "type": "string"
-    },
-    "planLabel": {
-      "description": "the target plan display name",
-      "type": "string"
-    },
-    "plans": {
-      "description": "available paid plans ({id, name, priceUsd, credits}) when listing",
-      "items": {},
-      "type": "array"
-    },
-    "url": {
-      "description": "the ready-to-pay Stripe Checkout URL (checkout mode)",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations: agents never spend money directly, nothing is charged until a human pays, new subscribers receive a Stripe Checkout URL, downgrades are handled by a person, and members get a specific message. These are non-obvious consequences not inferable from readOnlyHint/destructiveHint flags.

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 front-loaded with the core purpose and then walks through each usage scenario. It is longer than strictly minimal, but every sentence carries distinct information about plan listing, payment, downgrades, or member behavior. The only minor issue is the density of capitalized emphasis, which slows reading slightly.

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?

For a tool with no output schema, the description explains the return outcomes for every branch: plan list, Stripe Checkout URL, exact human-step instructions for downgrades, and an ask-admin message. Combined with full parameter schema coverageuj, an agent has everything needed to invoke it correctly across all cases.

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 description coverage is 100%, and the schema already documents that `plan` can be omitted to list plans and that `period` defaults to monthly with yearly offering 2 months free. The description reinforces the plan-omission flow but doesn't add meaning beyond the schema for either parameter.

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 opens with a precise verb and resource: 'Change this account's SUBSCRIPTION plan (admin only).' It distinguishes itself from related siblings like billing_status and buy_credits by focusing on subscription plan changes and explicitly covering admin/member access rules.

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?

It gives explicit call patterns: call with no argument to list plans, then call again with `plan` set. It also specifies the alternative path for existing paid plans or downgrades (human action in Settings -> Billing), and tells members to ask an admin. This is thorough, actionable guidance.

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