Skip to main content
Glama
Sign In

ARYSPHERE x402 chain reads and token verdicts

by com.arysphere
OverviewDiscussionsAdmin

x402_q_verdict_v1__dao_proposal_preview

Read-only

DAO Proposal Preview: decoded targets, proposal state, votes and timelock delay for one OpenZeppelin Governor proposal on Ethereum or Base. Check this first. Returns: a DAO proposal preview on one OpenZeppelin Governor proposal: the decoded targets and call data the buyer posts, the proposal state, vote totals, quorum and timelock delay read from the chain, and whether each target is verified. No verdict, no model.

Price: $0.002 USDC per call, paid by x402 (Base, Polygon or Arbitrum). POST https://api.arysphere.com/v1/ventures/x402_q_verdict_v1/dao_proposal_preview. Same payment terms as that HTTP route. Call once with no payment. The result is the payment terms. Retry the same call with the signed payment at _meta["x402/payment"].

Input Schema

NameRequiredDescriptionDefault
chainYesthe chain the Governor is on
valuesYesthe wei sent with each call, decimal strings, one per target
targetsYesthe proposal's target contracts, in order, 0x + 40 hex each
governorYesthe Governor contract, 0x + 40 hex
calldatasYesthe call data for each target, 0x hex, one per target
descriptionNooptional, the description text, for display only
descriptionHashYeskeccak256 of the proposal description, 0x + 64 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / description
      Added value: +"One OpenZeppelin Governor proposal, named by the chain, the Governor and the exact propose() arguments (they hash to the proposal id, checked on chain). Copy them from the ProposalCreated event or the proposal page."
    • addedInput schema / properties / calldatas
      Added value: +{
+  "description": "the call data for each target, 0x hex, one per target",
+  "items": {
+    "pattern": "^0x([0-9a-fA-F]{2})*$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / chain
      Added value: +{
+  "description": "the chain the Governor is on",
+  "enum": [
+    "ethereum",
+    "base"
+  ]
+}
    • addedInput schema / properties / description
      Added value: +{
+  "description": "optional, the description text, for display only",
+  "maxLength": 2000,
+  "type": "string"
+}
    • addedInput schema / properties / descriptionHash
      Added value: +{
+  "description": "keccak256 of the proposal description, 0x + 64 hex",
+  "pattern": "^0x[0-9a-fA-F]{64}$",
+  "type": "string"
+}
    • addedInput schema / properties / governor
      Added value: +{
+  "description": "the Governor contract, 0x + 40 hex",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}
    • addedInput schema / properties / targets
      Added value: +{
+  "description": "the proposal's target contracts, in order, 0x + 40 hex each",
+  "items": {
+    "pattern": "^0x[0-9a-fA-F]{40}$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / values
      Added value: +{
+  "description": "the wei sent with each call, decimal strings, one per target",
+  "items": {
+    "pattern": "^[0-9]{1,78}$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / required
      Added value: +[
+  "chain",
+  "governor",
+  "targets",
+  "values",
+  "calldatas",
+  "descriptionHash"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that by disclosing the x402 price ($0.002 USDC), accepted payment chains, the two-step 402 challenge flow, the HTTP route, and the fact that everything is read from chain rather than computed by a model. It does not cover failure modes (bad proposal hash, unverified target, revert) which keeps it from a 5. No contradiction: reading chain state is consistent with readOnlyHint even though a payment is settled.

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?

The operative content is front-loaded in the first sentence and the payment mechanics are clearly separated, but the 'Returns:' sentence restates the opening nearly verbatim ('a DAO proposal preview on one OpenZeppelin Governor proposal') before adding the return list, which is avoidable duplication.

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?

With 7 parameters, 6 required, no output schema and no destructive side effects, the description supplies everything an agent needs: what goes in (exact propose() arguments, sourced from ProposalCreated), what comes out (targets, state, votes, quorum, timelock, verification flags), and how to pay. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema carries the baseline; the description adds real cross-field meaning the schema cannot express — that targets, values and calldatas must be the exact propose() arguments, that they hash to the proposal id, that the hash is checked on chain, and where to copy them from (ProposalCreated event). That is genuine semantic lift above the field-level descriptions.

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?

The first sentence names a specific verb-and-resource pair (preview of one OpenZeppelin Governor DAO proposal), scopes it to Ethereum or Base, and enumerates the exact payload: decoded targets, proposal state, votes, timelock delay. The line 'No verdict, no model' plus 'Check this first' cleanly separates it from the sibling dao_proposal_verdict.

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?

'Check this first' plus 'No verdict, no model' implicitly routes an agent needing an actual judgment to the verdict sibling, and the payment handshake instruction ('Call once with no payment... Retry the same call with the signed payment') tells the caller exactly how to sequence the two calls. What's missing is an explicit naming of the alternative tool under a stated condition, so it stops just short of a 5.

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

All ARYSPHERE x402 chain reads and token verdicts 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