Skip to main content
Glama

moltbound_complete_purchase

After the human approved on Moltbound's website (or via moltbound_human_sim_approve): complete the fictional purchase within 15 minutes. Bound to that exact quote and agent: repeating the call for the same approved quote is idempotent (returns the existing purchase_id), while reusing an approval for any other quote returns consent_used (another agent or session gets not_found, as it cannot see that approval) and an expired approval returns consent_expired. On a timeout the state is unknown, not failed: repeat the same call, which is safe. The reply includes attempts (how many purchase calls this approval has had). SANDBOX: use fictitious data only. Do not enter real personal details.

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": {
      "session_token": "<session_token>",
      "consent_request_id": "<consent_request_id>"
    },
    "name": "moltbound_complete_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_tokenYesFrom moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify
consent_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session_token / description
      Previous value: -"From moltbound_start_session or moltbound_human_sim_verify"New value: +"From moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so thoroughly: idempotency semantics per approved quote, cross-agent visibility limits (another agent gets not_found), expiry behavior (consent_expired), timeout being 'unknown, not failed', and a sandbox warning against real personal data. It also discloses that the reply contains an attempts counter.

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?

Every sentence carries new information — timing, idempotency, error codes, timeout recovery, sandbox restriction — with the prerequisite front-loaded. The middle sentence is long with stacked parentheticals, slightly reducing scanability, but there is no filler.

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?

There is no output schema or annotations, so the description must cover return values and failure modes — it names purchase_id, attempts, consent_used, consent_expired, and not_found, and explains timeout ambiguity. For a two-parameter mutation with no structured support, this is essentially complete.

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 coverage is 50%: session_token is documented in the schema, while consent_request_id is not. The description does compensate by explaining the binding behavior of the approval (tied to exact quote and agent, idempotent on replay), but it doesn't state where consent_request_id comes from or its format. Adequate but leaves a real gap.

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 opens with a specific verb and resource ('complete the fictional purchase') and states its prerequisite (human approval on the website or via moltbound_human_sim_approve). It clearly distinguishes itself from an approval tool, though it never names moltbound_purchase_status as the way to check results afterward, leaving that sibling relationship implicit.

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 gives clear usage conditions: call only after approval, and within 15 minutes. It also gives explicit retry guidance for timeouts ('repeat the same call, which is safe'), and error-code routing for reused approvals (consent_used, not_found, consent_expired). It stops short of naming an alternative tool for status polling or for obtaining an approval in the first place.

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