Skip to main content
Glama

Buy a tool (exclusive)

buy_product

Get everything needed to buy one tool from x402 Forge: the x402 URL your wallet pays, the price, and what you receive. Each tool is sold once, to one owner: you get a small x402 server with the tool, Forge stops selling it, and your copy is listed under your wallet. This call itself is free and does not pay; pay the returned buy_url with an x402 client (for example an x402 fetch or payment tool, or the Fizzl Agent Wallet).

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": {
      "slug": "<slug>"
    },
    "name": "buy_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe tool's slug, from search_products
formatNozip (default) or json files

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exclusive one-owner sale model, that Forge stops selling after purchase, that ownership is listed under the buyer's wallet, and that this call performs no payment. It omits failure behavior (e.g., what happens if the tool is already sold) and any auth requirements beyond having a wallet.

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?

Three sentences, front-loaded with what the call returns before explaining the exclusive-sale mechanics and the free-vs-pay distinction. Slightly wordy in the payment-client examples but every sentence carries useful information.

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

Completeness4/5

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

There is no output schema, so the description appropriately explains what comes back (buy_url, price, what you receive). Combined with the exclusivity semantics, an agent has enough to call it and act on the result; only error/edge-case behavior is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (slug, format) are already documented, including the enum and default. The description adds no parameter-level meaning at all, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Get everything needed to buy one tool from x402 Forge') and enumerates the returned artifacts (x402 URL, price, deliverables). It implicitly separates itself from payment execution by saying 'This call itself is free and does not pay', though it never names a sibling tool explicitly.

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?

It tells the agent exactly what to do next: pay the returned buy_url with an x402 client, and even names example clients. It doesn't state prerequisites such as needing a wallet or what to do if the tool is already sold, so it stops short of a full when/when-not guide.

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