geld machen x402 agent utilities

Bazaar Readiness Check: x402 Index + Fix-JSON

bazaar-check

Read-onlyIdempotent

Audit an x402 endpoint for CDP Bazaar indexing: 402 header compliance, bazaar schema, quality issues. Use when your x402 endpoint is not showing up in the CDP Bazaar. Not for general URL metadata (use url-fingerprint). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.05 Base USDC via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: https x402 endpoint URL.

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: https x402 endpoint URL."

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.5/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent, non-destructive read (readOnlyHint, idempotentHint, destructiveHint=false). The description adds genuinely non-obvious behavior: a free sample is returned with the paid URL and pay steps at no charge, while the full result costs $0.05 Base USDC via x402. That pricing/return-flow disclosure is above what the structured fields convey.

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 dense sentences, front-loaded with the purpose, then the trigger, then the exclusion, then the payment/return model. No filler and nothing repeated from the name or annotations.

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 documentation is not required, yet the description still clarifies the free-vs-paid result split and the payment mechanism. Combined with exhaustive purpose and exclusion guidance, an agent has everything needed to select and invoke it.

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 description coverage is 100% and the single 'query' parameter is already documented as the https x402 endpoint URL. The description implies the same input but adds no format, syntax, or validation detail beyond the schema, so the 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 specific verb and resource — auditing an x402 endpoint for CDP Bazaar indexing — and enumerates the checks performed (402 header compliance, bazaar schema, quality issues). It also explicitly distinguishes itself from the sibling url-fingerprint, so an agent can route correctly without opening either schema.

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?

Gives an explicit trigger ('Use when your x402 endpoint is not showing up in the CDP Bazaar') and an explicit exclusion with the alternative named ('Not for general URL metadata (use url-fingerprint)'). This is the when/when-not/alternative pattern at full strength.

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?