Skip to main content
Glama

GrowVib: Social Media Growth

create_paid_order

DestructiveIdempotent

Place an order and pay for it with USDC on Base or Solana, with no GrowVib account and no human in the loop, using the x402 payment protocol. Call it FIRST without the payment argument: it returns the exact payment requirements, one accepts entry per network (amount in atomic units, asset, recipient, network, and for Solana the facilitator's feePayer). Pick the network your wallet is on: sign an EIP-3009 transferWithAuthorization (Base) or build and sign the USDC transfer transaction (Solana) for exactly those requirements, then call it AGAIN with the same arguments plus payment set to the signed x402 payment payload. Anything paid above the order's price stays as spendable balance on the wallet's account, so many small orders can be paid for with one settlement. If a call reports that the payment is still being confirmed, do NOT sign and send a new payment: the first one may already have gone through. Use get_quote first if you only want a price.

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": {
      "quantity": "<quantity>",
      "link": "<link>"
    },
    "name": "create_paid_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe target link the order is delivered to.
postsNoOnly for a subscription option on an auto-delivery service (get_quote tells you when one is needed): how many of the target's future posts to cover. The quantity is then the amount per post and the price is posts times that amount. Omit for every ordinary option.
paymentNoThe signed x402 v2 payment payload. Omit on the first call to receive the payment requirements.
quantityYesQuantity to order.
service_idNoThe service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service.
agent_tokenNoThe agent_token from a previous order's result. Send it INSTEAD of `payment` to pay out of the balance you already hold, with no new signature and nothing on chain. Requires `idempotency_key`. If your balance does not cover the order you get the payment requirements back as usual.
idempotency_keyNoA value unique to this order attempt (a UUID is fine), required when using `agent_token`. Sending the same key again returns the SAME order instead of buying a second time, so a retry after a timeout is safe.
service_option_idNoThe plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_option_id / description
      Previous value: -"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service."
  2. Changed3 schema fields changed
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id from search_catalog."New value: +"The service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service."
    • changedInput schema / properties / service_option_id / description
      Previous value: -"Optional specific service option id; defaults to the service's primary option."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."
    • changedInput schema / required
      Previous value: -[
      -  "service_id",
      -  "quantity",
      -  "link"
      -]New value: +[
      +  "quantity",
      +  "link"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / posts
      Added value: +{
      +  "description": "Only for a subscription option on an auto-delivery service (get_quote tells you when one is needed): how many of the target's future posts to cover. The quantity is then the amount per post and the price is posts times that amount. Omit for every ordinary option.",
      +  "type": "number"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (openWorld, destructive, idempotent), the description discloses real operational behavior: no account or human approval required, overpayment is retained as spendable balance, and a payment reported as still confirming must NOT be re-signed. That last warning is genuinely non-obvious and valuable. It stops short of describing what the returned order object contains, but a 4 is warranted for the concrete failure-mode guidance.

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 core action and the two-call flow before the per-network signing details, which is the right order for an agent. It is dense and long, but nearly every sentence carries load-bearing instructions; only the network-signing specifics feel slightly more verbose than needed.

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 8 parameters, nested objects, no output schema, and a protocol-driven retry pattern, this description supplies everything needed to call correctly: sequencing, network choice, signing requirements per chain, idempotency safety, and pending-payment handling. No output schema exists so no return-value explanation is owed.

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 a baseline 3 applies, and the description earns above that by explaining the sequencing constraint on `payment` (omit first, send second) and the balance-vs-signature tradeoff between `agent_token` and `payment`, which the schema only partly conveys. It does not elaborate on `posts` or `service_option_id` beyond what the schema already states.

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 ('Place an order and pay for it with USDC on Base or Solana'), names the payment protocol, and separates itself from get_quote by noting the quote-first path. An agent can tell immediately this is the money-moving purchase tool rather than the pricing tool.

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?

Gives an explicit two-phase procedure: call first without `payment` to obtain the `accepts` requirements, sign per network, then call again with the same arguments plus the payload. It also names the alternative path (agent_token instead of payment) and routes price-only inquiries to get_quote, so both when-to-use and when-not are covered.

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