geld machen x402 agent utilities

Red-Flag Scan: 12 Sketchy Side-Income Signals

red-flag-scan

Read-onlyIdempotent

Scan one offer/pitch for 12 evidence-quoted scam red flags plus live URL anchors (HTTP/TLS/DNS, RDAP domain age). Use when you must decide whether a specific offer or seller page is a scam before paying or replying. Not for ranking several offers by number (use offer-score) or a generic checklist without analysing your text (use deal-brief). Pick this when the question is 'is THIS offer a scam?'. Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.25 Base USDC via x402.

Input Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: offer text; append ' \| https://…' to include the offer URL.

Output 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.
`ready_request`	No	Exact 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.

Changed1 schema field changedOct 7, 2026

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."
+}

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: offer text; append ' | https://…' to include the offer 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 cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), but the description adds real value beyond them: the free-sample vs paid-result split, the exact price ($0.25 Base USDC via x402), and that no charge occurs on this call. That payment/auth context is the key operational fact an agent needs before invoking, though it does not discuss latency or rate limits.

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 tight sentences, front-loaded with what it does and followed by routing exclusions and the payment flow. No filler and every clause carries decision-relevant information.

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 structure need not be described, yet the description still clarifies the free-sample vs paid-URL/pay-steps split. Together with the explicit sibling routing and cost, an agent has everything needed to select and call this tool correctly.

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 coverage is 100% and there is only one parameter, whose description already documents the offer-text format and the ' | https://…' URL-append convention. The description adds no syntax or format 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 ('scan one offer/pitch') and enumerates exactly what it produces (12 evidence-quoted red flags plus live URL anchors covering HTTP/TLS/DNS and RDAP domain age). It also explicitly contrasts itself with the closest siblings (offer-score, deal-brief), so an agent can route without opening any 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 when-to-use ('decide whether a specific offer or seller page is a scam before paying or replying'), explicit when-not-to-use cases, and names the two alternative tools with the conditions that select them. It even restates the routing question as 'is THIS offer a scam?', leaving nothing to inference.

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

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

Need Help?