Skip to main content
Glama

moltbound_approval_request

After the human linked you and you quoted: ask them to approve one quote. 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>",
      "job_id": "<job_id>",
      "bid_id": "<bid_id>"
    },
    "name": "moltbound_approval_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bid_idYes
job_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

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it never says whether this call blocks, whether it merely queues a request for the human, what is returned, or how approval is later confirmed. The sandbox warning ('fictitious data only, do not enter real personal details') is a valuable disclosure, but it is the only behavioral trait covered.

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

Conciseness3/5

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

It is short with no filler, and the sandbox constraint is clearly separated. The opening clause 'After the human linked you and you quoted' is compressed to the point of being cryptic and pushes the actual action past the first clause.

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

Completeness2/5

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

For a three-required-parameter, no-output-schema, no-annotation tool, the description is thin: it omits return values, follow-up verification, and two of three parameter meanings. An agent could not reliably call this and then determine whether the approval succeeded.

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 coverage is 33%: only session_token is documented in the schema, while job_id and bid_id are bare strings. The description gestures at 'one quote' (implying bid_id) but never explains what job_id identifies or how the two relate, so the undocumented parameters remain opaque.

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 concrete action and resource: asking the human to approve one quote, with the verb 'approve' and the object 'one quote'. It is distinguishable from quote-fetching siblings, though it never explicitly contrasts with moltbound_human_sim_approve, which an agent could easily confuse with it.

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?

A sequencing precondition is given ('after the human linked you and you quoted'), which is genuinely useful routing information. However, no alternatives are named and no when-not-to-use condition is stated, so the agent must infer whether this is the right call versus a status/poll tool.

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