Skip to main content
Glama

moltbound_purchase_status

Poll the status of a fictional purchase by purchase_id until 'bound'. Returns partner's policy_number and attempts (every purchase call made with this approval, accepted or refused). 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>",
      "purchase_id": "<purchase_id>"
    },
    "name": "moltbound_purchase_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_idYes
session_tokenYesFrom moltbound_start_session, moltbound_human_sim_headless or moltbound_human_sim_verify

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

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does meaningful work: it discloses the returned fields (policy_number and attempts), defines 'attempts' precisely as every purchase call made with this approval, accepted or refused, and states the terminal status. It still omits the set of possible non-terminal statuses and any error/auth behavior, which are real gaps for a polling tool with zero annotation coverage.

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 short sentences, front-loaded with the action and terminal condition, then the return payload, then the sandbox constraint. Dense but every sentence earns its place; only the nested parenthetical definition adds slight density.

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?

With no output schema and no annotations, the description supplies return fields, the polling termination condition, and a sandbox safety constraint, which is solid coverage for a two-parameter tool. It is not fully complete because purchase_id provenance and the enumeration of intermediate statuses are left unstated.

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 purchase_id has no schema description. The description references purchase_id but never says where it comes from or its format, so it does not fully compensate for the undocumented parameter.

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 pairs a specific verb and resource ('Poll the status of a fictional purchase') with the identifier to use ('by purchase_id') and the terminal condition ('until bound'), so an agent knows exactly what this call does. It stops short of explicitly naming a sibling like moltbound_complete_purchase as the alternative, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Poll ... until bound' is an implied usage instruction: call repeatedly until a terminal state is reached. However, no polling cadence, no when-not guidance, and no named alternative (e.g., the tool that initiates or completes the purchase) are given, so the agent must infer the surrounding workflow.

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