Skip to main content
Glama

create_crypto_invoice

Create a fixed-price crypto invoice on a supported network. One transfer, 100% to the configured HOBO Works owner address, no split or commission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>",
      "asset_id": "<asset_id>"
    },
    "name": "create_crypto_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes
product_idYes
owner_briefNoFor a service: the owner's goal, supplied inputs, constraints, and expected deliverable.
buyer_walletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / owner_brief
      Added value: +{
      +  "description": "For a service: the owner's goal, supplied inputs, constraints, and expected deliverable.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / asset_id / enum
      Previous value: -[
      -  "ethereum_usdc",
      -  "base_usdc",
      -  "arbitrum_usdc",
      -  "optimism_usdc",
      -  "polygon_usdc",
      -  "linea_usdc",
      -  "sei_usdc",
      -  "arc_usdc",
      -  "ethereum_usds",
      -  "base_usds",
      -  "ethereum_eth",
      -  "base_eth",
      -  "arbitrum_eth",
      -  "optimism_eth",
      -  "bsc_bnb",
      -  "polygon_pol"
      -]New value: +[
      +  "ethereum_usdc",
      +  "base_usdc",
      +  "arbitrum_usdc",
      +  "optimism_usdc",
      +  "polygon_usdc",
      +  "linea_usdc",
      +  "sei_usdc",
      +  "arc_usdc",
      +  "ethereum_usds",
      +  "base_usds",
      +  "ethereum_eth",
      +  "base_eth",
      +  "arbitrum_eth",
      +  "optimism_eth",
      +  "bsc_bnb",
      +  "polygon_pol",
      +  "solana_sol",
      +  "bitcoin_btc"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "product_id",
      -  "asset_id",
      -  "buyer_wallet"
      -]New value: +[
      +  "product_id",
      +  "asset_id"
      +]
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: a single transfer, 100% to the configured owner address, no split or commission. It omits what happens on creation (invoice expiry, returned payment address/amount) and any auth requirements, leaving real gaps for a mutation tool.

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?

Two tight sentences with the core action front-loaded and the payment-routing detail second. No filler, though the second sentence is more about payout mechanics than invocation guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description must cover return values and safety, and it does not. For a 4-parameter creation tool, an agent still lacks the invoice response shape, expiry behavior, and the meaning of two undocumented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% across 4 parameters. The description adds nothing about product_id or buyer_wallet, and only the asset_id enum and owner_brief's own schema text document the rest. 'Fixed-price' hints at pricing behavior but does not explain how product_id drives the amount.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a fixed-price crypto invoice') plus the network scoping, which cleanly separates it from create_stripe_checkout among the siblings. It stops short of naming the alternative explicitly, but the crypto framing is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the crypto/network framing suggests when to pick this over create_stripe_checkout, but there is no explicit when-to-use, when-not, or prerequisite statement. An agent must infer the routing decision.

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.

Resources