Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

collab_think

NeuroDread host draft response (no public publish), with optional multi-turn session_id continuity Unpaid calls return HTTP 402 requirements; retry with payment_signature.

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": {
      "prompt": "<prompt>"
    },
    "name": "collab_think"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYes
order_refNo
credit_keyNo
session_idNo
wallet_proofNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior3/5

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

Beyond the annotations, the description usefully discloses two real behaviors: output is a draft and not publicly published (consistent with destructiveHint=false), and unpaid invocations fail with HTTP 402 and must be retried with payment_signature. That payment-failure/remediation detail is genuine value the structured fields do not carry. However it says nothing about what a paid call actually returns, whether a session persists across calls, or cost, so the disclosure is partial.

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

Conciseness2/5

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

It is short, but it is a run-on fragment with a missing period and mixed concerns (product name, publish policy, session behavior, HTTP error handling) jammed into two clauses. The most informative content, the 402/payment retry path, is buried at the end rather than front-loaded.

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?

This is a non-read-only, open-world, non-idempotent tool with 7 parameters, no output schema, and no schema descriptions, so the description carries the full documentation burden. Covering only draft-vs-publish and the 402 retry leaves the payment/credit model, session semantics, and five parameters unexplained.

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% across 7 parameters, so the description must compensate and it only does so for two: session_id (multi-turn continuity) and payment_signature (retry after 402). The required prompt, plus order_ref, credit_key, wallet_proof, and wallet_address have no explanation anywhere, leaving the caller to guess at payment/identity wiring.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"NeuroDread host draft response (no public publish)" gives a hint that a draft artifact is produced without publishing, but "NeuroDread host" is opaque jargon and the verb phrase is not a recognizable action (generate? persist? delegate?). An agent cannot tell from this text how collab_think differs from collab_access_check or any of the payment/atlas 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?

The only usage cues are that session_id enables multi-turn continuity and that a 402 should be retried with payment_signature. There is no statement of when to choose this tool over its siblings, no prerequisites, and no exclusions; the caller must infer the entire selection policy.

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