Skip to main content
Glama

moltbound_human_sim_headless

TEST-ONLY simulated person with no email (sandbox): one call returns a session_token (you, the agent) and a human_sim_token (the simulated person) so you can test quote, approval, decline and purchase without an inbox or passkey. Not a real person, never billable, expires in 24 hours. SANDBOX: use fictitious data only. Do not enter real personal details.

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

Input Schema

NameRequiredDescriptionDefault
agent_nameNo
capabilityNoquote_and_bind

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 that no inbox or passkey is required, that the artifact expires in 24 hours, that it is never billable, and that it is sandbox-scoped. It omits idempotency/repeat-call behavior and whether tokens can be refreshed after expiry.

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 compact sentences, front-loaded with what the tool is and what it returns. The parenthetical '(you, the agent)' and the closing sandbox warning are both load-bearing, so very little is wasted.

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 2-parameter tool with no output schema, it does describe the return values and the sandbox constraints, which is the important part. The gap is that neither input parameter is explained and the relationship to the non-test human_sim siblings is left implicit, so an agent cannot fully predict the effect of 'capability'.

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?

Schema description coverage is 0% and the description never mentions agent_name or capability. The enum values 'quote_only' and 'quote_and_bind' are never explained, so an agent must guess what the capability choice changes in the returned token's behavior.

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 names a specific resource – a TEST-ONLY simulated person in a sandbox – and states exactly what a single call produces (a session_token for the agent and a human_sim_token for the simulated person). The 'TEST-ONLY'/'Not a real person' framing does help separate it from production siblings, but it never names the closest alternative (e.g. moltbound_human_sim_start) for contrast.

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 a clear use case: test quote, approval, decline and purchase flows without an inbox or passkey, and adds a hard constraint ('use fictitious data only. Do not enter real personal details'). It stops short of explicit when-not-to-use routing or pointing at the real-path sibling tools.

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