Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

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 checkout_url (crypto checkout page on eqvps.com) 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pay_invoice"
  }
}

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.6/5.0
Behavior5/5

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

Goes well beyond the annotations: states that money is spent, that a balance-covered invoice is charged instantly and triggers server creation (with list_vps polling), that the crypto path charges nothing up front and settles on-chain, and that retries are safe because a repeat returns 409. That retry note refines rather than contradicts idempotentHint=false — the call does not succeed twice, but it cannot double-charge. Auth requirement (token) is also disclosed.

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-loaded with the money warning and outcome branches, and nearly every clause carries unique operational detail. The closing sentence largely restates the balance-vs-checkout logic already given, which is the only real 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?

With no output schema, the description compensates by naming the returned fields (paid_from_balance, status, balance, checkout_url) and the 409 error case, plus the post-payment side effect on servers. 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 already 100%, so the baseline is 3; the description adds real value by stressing that invoice_id must be passed exactly as returned with the example code format, and it is consistent with the schema's plain-number fallback. No contradiction, though the schema labels the field optional while the description implies it is needed to pay anything.

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?

"Pay an owned, unpaid invoice" gives a specific verb plus resource and immediately narrows scope (owned, unpaid), which separates it from topup_balance and order_vps. An agent can tell what this does without opening the schema.

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?

Explicit gating is provided: confirm with the human first, and the two outcome branches (balance-covered vs crypto checkout) are spelled out, along with the special case that top-up invoices always go crypto. It stops short of naming a sibling to use instead when the user actually wants to add funds or place a new order, so it is strong context rather than full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.