pay_invoiceInitiate payment for an owned, unpaid invoice. Returns a PayRam checkout_url; the invoice settles (and the VPS provisions) automatically once the on-chain payment confirms.
| Name | Required | Description | Default |
|---|---|---|---|
| invoice_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses return of checkout_url and automatic settlement, but doesn't cover errors or idempotency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no fluff, front-loaded with action and result.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers action, return, and side effects adequately for a simple tool; missing error handling details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No description for the invoice_id parameter despite 0% schema coverage; description doesn't elaborate on its meaning even though it's inferable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it initiates payment for an owned unpaid invoice, distinguishes from siblings like topup_balance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly requires invoice to be owned and unpaid, but lacks explicit when-not-to-use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are cleanly separated into auth, billing, VPS lifecycle, tickets, and delegation, and each maps to a distinct resource/action. A few pairs like set_password vs reset_password and pay_invoice vs topup_balance share surface similarity, but their descriptions draw clear boundaries.
Naming is strongly consistent with verb_noun snake_case patterns such as order_vps, list_tickets, and revoke_delegation. Minor deviations are the bare CLI-style verbs login and whoami, plus the slightly awkward topup_balance, but these do not undermine the overall pattern.
27 tools is on the high side, but the server covers several distinct subdomains—account management, billing, VPS operations, support tickets, and delegations—and each tool appears to earn its place. The count is heavy but not unreasonable for the breadth of functionality exposed.
Core workflows are covered end-to-end: account creation/login, ordering and provisioning, power/reinstall/cancel, ticket conversations, and delegation management all have the necessary operations. Minor gaps exist, such as no change-password tool, no explicit RDNS/console tool despite delegation mentioning them, and no plan upgrade/downgrade tool.