Skip to main content
Glama
Sign In

Verse by A-to-Mind

by io.github.atomeam
OverviewDiscussionsAdmin

Ask Verse (paid answer) (0.05 USDC, x402)

paid_answer

Verse answers a question: a direct answer from Verse's model, with the Wikipedia source linked when one matches. One call, one answer. Costs 0.05 USDC on Base (eip155:8453) per call, paid with x402 over MCP: call it without payment to get the PaymentRequired terms in structuredContent, then call it again with the signed PaymentPayload in params._meta["x402/payment"]. The settlement comes back in result._meta["x402/payment-response"]. A call that cannot be done (bad input, the service busy) is never charged. The same service over HTTP: POST https://a-to-mind.com/api/x402/answer.

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": {
      "ask": "<ask>"
    },
    "name": "paid_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
askYesthe question, 3 to 600 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds the behavior that actually matters: exact price (0.05 USDC on Base eip155:8453), the x402 payment flow, where settlement appears (result._meta["x402/payment-response"]), and the crucial guarantee that failed or busy calls are never charged. It also discloses the equivalent HTTP endpoint. This is substantially more than the annotations carry, with no contradiction of them.

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

Conciseness5/5

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

Front-loaded with what the tool returns, then price, then the payment handshake, then the non-charge guarantee, then the HTTP fallback. Four sentences, no filler, and the meta-key paths are given verbatim where an agent needs them.

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

Completeness5/5

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

For a one-parameter paid tool with no output schema, the description covers everything an agent needs to invoke it correctly: cost, currency, chain, the unpaid-then-paid call pattern, settlement location, and failure semantics. Nothing material is missing.

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?

The single parameter is fully documented in the schema (question, 3–600 characters), so the schema does the heavy lifting. The description adds context about the answer's nature and Wikipedia sourcing but nothing about the parameter itself. Baseline 3 applies at 100% schema coverage with one param.

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?

"Verse answers a question: a direct answer from Verse's model, with the Wikipedia source linked when one matches" is a specific verb+resource with a stated output shape, and "One call, one answer" bounds the scope. It never differentiates itself from the closely-named sibling ask_void or the other paid_* tools, so an agent must infer that this is the paid counterpart.

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?

Usage is only implied (you have a question and are willing to pay). The description does spell out the two-step payment handshake — call unpaid for PaymentRequired, then re-call with params._meta["x402/payment"] — which is real procedural guidance. But there is no explicit when-to-use-vs-alternatives routing (e.g., free ask_void, other paid_* endpoints), which is the main gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Verse by A-to-Mind toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources