merona — x402 settlement index

clean_stats

Read-onlyIdempotent

Get wash-adjusted x402 settlement volume per chain — spend that survives removal of funded loops and self-dealing cycles, which can differ from raw transfer totals by orders of magnitude. Returns clean settlement count, clean volume in USD and an as-of date per chain. Takes no arguments. Free, no key. These are the figures published on merona.io.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Scope and method pointer.
`clean`	No	One entry per chain.
`error`	No	Present only on backend failure.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"This tool takes no arguments."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Wash-adjusted settlement figures per chain.",
+  "properties": {
+    "clean": {
+      "description": "One entry per chain.",
+      "items": {
+        "properties": {
+          "as_of": {
+            "description": "Measurement date (UTC).",
+            "type": "string"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "clean_settlements": {
+            "type": "integer"
+          },
+          "clean_volume_usd": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Present only on backend failure.",
+      "type": "string"
+    },
+    "note": {
+      "description": "Scope and method pointer.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the calculation logic (wash-adjusted, removing funded loops and self-dealing cycles), the potential orders-of-magnitude difference from raw totals, and the return contents (clean settlement count, volume in USD, as-of date). It also emphasizes no cost and no API key, which are behavioral facts not captured by annotations.

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?

The description is three sentences long: first sentence states the purpose and key caveat, second sentence enumerates the return fields, and third sentence covers access requirements. Every sentence adds value; no filler words.

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?

Given the tool has no parameters and an output schema exists, the description is comprehensive. It explains what is returned, the statistical significance of the numbers, and the access requirements. It also addresses potential confusion about why these figures differ from raw transfer totals.

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?

The tool has zero parameters, so the schema is fully covered. The description explicitly states 'Takes no arguments', reinforcing the schema. Since there are no parameters to explain, this is a solid baseline for parameter semantics.

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 description uses a specific verb phrase 'Get wash-adjusted x402 settlement volume per chain' and clarifies the core value proposition (spend that survives removal of funded loops and self-dealing cycles). This clearly states what the tool does and differentiates it from siblings, which are unrelated tools.

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?

It provides implicit usage guidance by explaining the difference from raw transfer totals and indicating that these are the figures published on merona.io. It also states 'Takes no arguments. Free, no key' which sets expectations for usage. There is no explicit alternative exclusion, but the unique purpose is clear.

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

All merona — x402 settlement index tools Inspect

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

Need Help?