Skip to main content
Glama
hermoso-ai

Hermoso

Official

Buy credits

buy_credits

Top up your account with credit packs. List packs, get a quote, and charge your saved card or receive a Stripe checkout link.

Instructions

Out of credits? Top up with a credit PACK. Call with no argument to list the available packs (id · credits · price). If the account has a saved card and you have billing-admin rights, calling with pack quotes the exact charge and calling again with confirm:true AND the quote's quote_token charges the saved card instantly (same one-click top-up as the app — no redirect). If there's no saved card yet, you get a Stripe checkout URL to hand your human for the FIRST purchase; their card saves for one-click after that. Packs only; subscriptions are managed by a person in Settings → Billing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packNothe pack id to buy (e.g. pack-2k) — omit to list the available packs first
confirmNoset true to actually charge the saved card for `pack` (required for the one-click charge; ignored on the checkout-link path)
quote_tokenNothe quoteToken returned by the quote step — REQUIRED (with confirm:true) to charge; it binds the exact pack + price you quoted (10-minute validity) and makes a retried confirm idempotent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNotrue when a one-click top-up charge succeeded
urlNoStripe checkout URL for a first purchase (no saved card yet)
packsNoavailable credit packs ({id, credits, priceUsd}) when listing
quoteNothe one-click charge quote ({packId, credits, priceUsd, card}) awaiting confirm:true
packIdNothe pack id the checkout link buys
creditsNocredits added by a completed top-up (or bought by the checkout link)
amountUsdNoUSD amount of the checkout link
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false) and side effects (openWorldHint=true). The description adds rich behavior: two-step charge with quote, checkout URL path, billing-admin requirement, and idempotency via quote_token. No contradictions.

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 a single paragraph but logically structured: purpose, then two payment paths. Every sentence adds necessary information with no redundancy.

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 complex financial tool, the description covers prerequisites (billing-admin, saved card), two scenarios (first purchase vs recurring), quote validity, and where subscriptions are handled. Output schema exists.

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%, baseline 3. The description adds flow context (omit to list, confirm required for charge, quote_token binds quote) and clarifies behavior like idempotent retries.

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 verb (buy) and resource (credits), explaining it can list packs and execute purchases. It distinguishes from siblings like billing_status or upgrade_plan by detailing the credit-purchase flow.

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 says when to use (out of credits) and how to start (call with no argument). It explains two distinct usage paths based on payment method, though it does not explicitly list alternatives or say when not to use.

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