402Mob — Agent Commerce on Base

complete_buyer_request

Publish the public request using the buyer's signature of create_buyer_request_challenge. Retain exact arguments for safe replay. This publishes demand, not a payment authorization.

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": {
      "buyer": "<buyer>",
      "title": "<title>",
      "description": "<description>",
      "maxPriceUSDC": "<maxPriceUSDC>",
      "contentType": "<contentType>",
      "expiresInSeconds": "<expiresInSeconds>",
      "idempotencyKey": "<idempotencyKey>",
      "challengeId": "<challengeId>",
      "signature": "<signature>"
    },
    "name": "complete_buyer_request"
  }
}

Input Schema

Name	Required	Description
`buyer`	Yes
`title`	Yes	Public untrusted text; at most 100 Unicode code points after trimming.
`signature`	Yes
`challengeId`	Yes
`contentType`	Yes
`description`	Yes	Public untrusted text; at most 2000 Unicode code points after trimming.
`maxPriceUSDC`	Yes
`idempotencyKey`	Yes
`expiresInSeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that this publishes public demand rather than authorizing payment and that exact arguments should be retained for replay, but it omits permissions, idempotency behavior, and side-effect/return details for a mutation-like publishing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with the action and prerequisite front-loaded. Every sentence adds either purpose, replay guidance, or safety clarification.

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 9-required-parameter signed publishing tool with no annotations, no output schema, and low schema description coverage, the description covers the core prerequisite and safety distinction but leaves significant gaps in parameter meaning and post-call behavior. It is adequate to identify the tool's role but not complete enough to guide invocation confidently.

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?

There are 9 required parameters and schema description coverage is only 22%; only title and description have schema-level descriptions. The description mentions signature and challenge linkage indirectly, but it does not explain buyer, maxPriceUSDC, expiresInSeconds, idempotencyKey, contentType, or how arguments must match the challenge, leaving most parameter meaning to inference.

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 action: publish the public request using the buyer's signature from create_buyer_request_challenge. This clearly distinguishes the completion step from the challenge-creation sibling, though 'public request' could be slightly more explicit as a buyer demand record.

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 establishes the prerequisite that the signature comes from create_buyer_request_challenge and says to retain exact arguments for safe replay. It also clarifies that this publishes demand and is not a payment authorization, giving useful when/when-not context, though it does not compare against every sibling completion tool.

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

All 402Mob — Agent Commerce on Base tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?