geld machen x402 agent utilities

Base DeFi Snapshot: Balances + Gas + Protocol TVL/APY

defi-base-snapshot

Read-onlyIdempotent

Snapshot Base DeFi state: ETH+USDC balances, base fee/block and protocol TVL/APY proxies. Use when you need a one-call Base market/wallet context. Not for a single balance (use base-balance) or one tx (use base-tx-explain). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.03 Base USDC via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: optional 0x address.

Output Schema

TableJSON Schema

Name	Required	Description
`sku`	Yes
`note`	No
`payTo`	No
`price`	No
`method`	No
`network`	No
`paid_url`	Yes
`how_to_pay`	Yes
`teaser_url`	No
`your_input`	No
`free_teaser`	No	Free sample output of this SKU (truncated); null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / free_teaser

Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / query / description

Previous value: -"Optional input (e.g. url / address / text) to pass to the paid endpoint as ?q= or JSON body."New value: +"Input for the paid endpoint: optional 0x address."

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_pay": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "paid_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payTo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sku": {
+      "type": "string"
+    },
+    "teaser_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "your_input": {}
+  },
+  "required": [
+    "sku",
+    "paid_url",
+    "how_to_pay"
+  ],
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive) but the description adds the critical commercial behavior that structured fields cannot: it returns a free sample plus a paid URL and pay steps with no charge at snapshot time, and the full result costs $0.03 Base USDC via x402. For a monetized tool, this pricing/payment context is essential and non-obvious.

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?

Three sentences, front-loaded with purpose, then usage/exclusions, then the payment model. Every sentence earns its place with zero padding, and the most decision-critical routing info (when to use / not use) precedes the pricing detail.

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?

An output schema exists so return-value explanation is not needed, annotations handle the safety profile, and the description covers the remaining gaps: what data is bundled, sibling disambiguation, and the x402 payment flow including cost and that this call is free. Nothing an agent needs to invoke it correctly 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?

Only one optional parameter (query) with 100% schema description coverage already explaining it takes an optional 0x address. The description does not add format constraints or examples beyond 'optional 0x address', so the schema does the heavy lifting. Baseline 3 is appropriate.

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 the specific verb+resource ('Snapshot Base DeFi state') and enumerates the exact bundled outputs: ETH+USDC balances, base fee/block and protocol TVL/APY proxies. It also names the two sibling alternatives it is not, so an agent can differentiate it from base-balance and base-tx-explain without reading their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the use case ('when you need a one-call Base market/wallet context') and the exclusions with named alternatives ('Not for a single balance (use base-balance) or one tx (use base-tx-explain)'). This is textbook when-to-use/when-not-to-use guidance.

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

All geld machen x402 agent utilities 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?