Skip to main content
Glama

Order a tool in one sentence

order_product

How to have x402 Forge build a tool for you: describe it in one sentence, pay $1.00 with x402, and send it back with revise_order if something is missing. Does not place or pay for an order.

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": "order_product"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 real behavioral facts: a $1.00 charge, x402 as the payment rail, and that this tool itself does not transact. However, it never says what the call returns or that it takes no input, and 'describe it in one sentence' implies an input the tool does not accept, which will mislead an agent about how to invoke it.

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?

One compact sentence with the value proposition and price front-loaded, followed by the exclusion. No filler, though the clause order buries the actual 'what this tool returns' point entirely.

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

Completeness3/5

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

For a zero-parameter, no-annotation, no-output-schema tool, the description needs to explain both the invocation model and what comes back. It covers the pricing and workflow but leaves the return value and the mechanics of 'pay with x402' unexplained, which is a material gap for a paid tool.

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?

The input schema is empty, so the baseline would normally be high, but the description actively implies a parameter ('describe it in one sentence', 'pay $1.00') that has no corresponding field. That mismatch reduces clarity rather than adding meaning beyond the schema.

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

Purpose3/5

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

The description says it explains 'How to have x402 Forge build a tool for you', which is a specific enough purpose for an instructional tool, but it opens by restating the workflow rather than stating plainly what the tool does. It also sits in tension with its own name (order_product vs. 'Does not place or pay for an order'), so an agent must read carefully to realize this is guidance, not an ordering action.

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 explicitly gives a when-not ('Does not place or pay for an order') and names the follow-up alternative, revise_order, for when something is missing. What's missing is routing against the other transaction-flavored siblings like buy_product and try_product; the agent must infer which of those actually places an order.

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