Skip to main content
Glama
Sign In

EQVPS — VPS and code sandboxes for AI agents

by io.github.Poiuyhje
OverviewDiscussionsAdmin

Pay an invoice

pay_invoice
Destructive

Pay an owned, unpaid invoice. SPENDS MONEY — confirm with the human first. If the prepaid balance covers the whole invoice, it is paid from the balance right away (paid_from_balance: true, status: paid, new balance; ordered servers are then created automatically — poll list_vps). Otherwise nothing is charged and a PayRam crypto checkout_url is returned (paid_from_balance: false); the invoice settles automatically once the on-chain payment confirms. Balance top-up invoices are always paid by crypto. Safe to retry: an invoice is never charged twice (a repeat returns 409 Invoice is already paid). Requires: token. Pass invoice_id exactly as returned (a code like "2RUAWV4"). Pays from the balance if it covers the invoice; otherwise a human pays checkout_url.

Input Schema

NameRequiredDescriptionDefault
invoice_idNoOptional. Invoice id exactly as returned by order_vps / topup_balance, e.g. "2RUAWV4" (a plain number is also accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / invoice_id / description
      Previous value: -"Invoice id exactly as returned by order_vps / topup_balance, e.g. \"2RUAWV4\" (a plain number is also accepted)."New value: +"Optional. Invoice id exactly as returned by order_vps / topup_balance, e.g. \"2RUAWV4\" (a plain number is also accepted)."
  2. Changed5 schema fields changed
    • addedInput schema / properties / invoice_id / description
      Added value: +"Invoice id exactly as returned by order_vps / topup_balance, e.g. \"2RUAWV4\" (a plain number is also accepted)."
    • removedInput schema / properties / invoice_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / invoice_id / minLength
      Added value: +1
    • changedInput schema / properties / invoice_id / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / required
      Removed value: -[
-  "invoice_id"
-]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by explaining exactly what money moves, what happens when the balance is insufficient (nothing charged, checkout_url returned), the automatic server-creation side effect, and retry behavior returning 409 'Invoice is already paid'. The retry claim is in mild tension with idempotentHint=false, but is defensible because a repeat call returns an error rather than the original result, so it is not flagged as a contradiction.

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?

Front-loads the two things that matter most — what it does and that it SPENDS MONEY. It is dense with parenthetical asides rather than wasteful, but the single paragraph packs several branches together, which slows scanning slightly compared to a bulleted split.

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?

There is no output schema, and the description fully compensates by naming every returned field (paid_from_balance, status, balance, checkout_url) and the 409 failure case. Nothing an agent needs to call this safely or interpret the result is missing.

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%, so the baseline is 3, but the description reinforces the format requirement ('pass invoice_id exactly as returned, a code like "2RUAWV4"') and notes it originates from order_vps / topup_balance. It adds modest but real value about where the identifier comes from.

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?

States a specific verb and resource with scope qualifiers: 'Pay an owned, unpaid invoice.' An agent can immediately distinguish it from the sibling mutators that create invoices (order_vps, topup_balance) and from read-only tools like get_balance.

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?

Explicit preconditions and branches: confirm with the human first, invoice must be owned and unpaid, and balance top-up invoices must go through crypto rather than this path's balance branch. It also routes the agent to list_vps to observe the downstream effect, which is the correct follow-up tool.

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

All EQVPS — VPS and code sandboxes for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources