Skip to main content
Glama
Sign In

Verse by A-to-Mind

by io.github.atomeam
OverviewDiscussionsAdmin

Appraise an item from a photo (0.05 USDC, x402)

paid_appraise

Verse values an item from a photo: the vision model describes it and Verse gives an estimated value range with what it saw. People are never priced. One call, one appraisal. 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/appraise.

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": {
      "image": "<image>"
    },
    "name": "paid_appraise"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNowhat the item is, optional
imageYesa PNG, JPEG or WebP data URL, under 800 KB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the exact price (0.05 USDC), chain (eip155:8453), the params._meta['x402/payment'] handoff, where settlement appears (result._meta['x402/payment-response']), and the important guarantee that failed calls are never charged. Annotations only say it mutates/open-world; the description supplies the money-safety contract an agent needs before invoking a paid tool.

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?

Purpose is front-loaded in the first clause, followed by the payment mechanics and failure policy in a logical order. Slightly dense with protocol detail and the trailing HTTP endpoint line, but every sentence carries operational value and there is no filler.

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

Completeness4/5

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

With no output schema, the description does state what comes back (value range plus observed details) and where the settlement receipt lands, which covers the essentials for a paid one-shot call. It stops short of describing the response structure or error/settlement timing in detail.

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?

Schema coverage is 100%, with both 'image' (PNG/JPEG/WebP data URL under 800 KB) and 'note' already documented in the schema. The description adds only that the photo drives a vision-model description plus valuation, and does not elaborate on how 'note' influences the appraisal, so baseline 3 applies.

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

Purpose5/5

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

States a concrete verb and resource: 'Verse values an item from a photo', and specifies both the mechanism ('the vision model describes it') and the return ('an estimated value range with what it saw'). This is clearly distinguishable from siblings like paid_image or paid_answer without opening any schema.

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?

Gives explicit procedural guidance for the two-step x402 flow (call without payment to receive PaymentRequired terms, then re-call with PaymentPayload) and a scope rule ('People are never priced'). It does not say when to prefer this over sibling paid_* tools or what kinds of items are in scope, so it falls short of full alternative routing.

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