Skip to main content
Glama

geld machen x402 agent utilities

by dev.fly.geld-machen-x402
OverviewDiscussionsAdmin

Phantom Seller Scan: Is payTo Economically Dead?

phantom-seller-scan
Read-onlyIdempotent

Check whether an x402 URL's payTo actually receives Base USDC (economically live vs phantom). Use when before integrating or paying one unknown x402 endpoint you already have. Not for listing many vetted sellers (use phantom-allowlist) or finding new endpoints (use agent-lead-pack). Pick this when the question is 'is THIS URL real?'. 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

NameRequiredDescriptionDefault
queryNoInput for the paid endpoint: https x402 endpoint URL.

Output Schema

NameRequiredDescriptionDefault
skuYes
noteNo
payToNo
priceNo
methodNo
networkNo
paid_urlYes
how_to_payYes
teaser_urlNo
your_inputNo
free_teaserNoFree sample output of this SKU (truncated); null if unavailable.
ready_requestNoExact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / ready_request
      Added value: +{
+  "description": "Exact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client."
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / free_teaser
      Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}
  3. Changed1 schema field changed
    • 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."
  4. Changed1 schema field changed
    • 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"
+}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds non-obvious behavioral context: a free sample is returned, the paid URL and pay steps are exposed, and the full result costs $0.03 Base USDC via x402. That pricing/payment behavior is exactly the kind of thing structured fields do not convey, though pagination/response shape detail is absent.

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 scoping statement and exclusions are front-loaded and every sentence carries information. A couple of phrasings are slightly clunky ('Use when before integrating'), but 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?

An output schema exists, so return values need not be explained, and the description still summarizes what comes back (free sample plus paid URL and pay steps). With one simple parameter and full annotation coverage, the definition is essentially complete; only deeper result-format nuance 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?

There is a single parameter with 100% schema description coverage, so the schema already documents that 'query' is the x402 endpoint URL. The description adds only the framing that this is an unknown endpoint the caller already possesses, not new syntax or format detail — 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?

The description names a specific verb and resource — checking whether an x402 URL's payTo actually receives Base USDC (live vs phantom) — and explicitly distinguishes itself from phantom-allowlist and agent-lead-pack. An agent can identify the tool's exact job without opening the 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?

It states when to use it ('before integrating or paying one unknown x402 endpoint you already have'), when not to (listing many vetted sellers, finding new endpoints), and names the alternative tool for each exclusion. The selecting question is spelled out verbatim.

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 toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources