Skip to main content
Glama

moltbound_consent_link

Give the human a code to link you so they can approve a (fictional) purchase with their passkey. 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>"
    },
    "name": "moltbound_consent_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_priceNo
service_idNo
jurisdictionNoUS
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.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the sandbox constraint (fictitious data only) but says nothing about code expiry, what the human sees, whether the link is single-use, or what the tool returns.

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?

Two tight sentences with the core action front-loaded and the sandbox caveat following. No wasted wording, though it is arguably too terse given the undocumented parameters.

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 four-parameter tool with no annotations, no output schema, and 25% schema coverage, the description is far too thin. It omits parameter meaning, return behavior, and the linking flow's prerequisites.

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 only 25%: only session_token is documented. The description adds no meaning for max_price, service_id, or jurisdiction, leaving three of four parameters unexplained in both schema and description.

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?

States a specific verb and resource: give the human a code to link them so they can approve a purchase with their passkey. An agent can tell this is a linking/consent step distinct from approval_request or complete_purchase, though it doesn't explicitly name those siblings.

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

Usage Guidelines2/5

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

Usage is only implied by the phrase 'so they can approve a purchase.' There is no explicit when-to-use guidance, no prerequisites, and no statement of when to prefer this over moltbound_approval_request or moltbound_human_sim_approve.

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