geld machen x402 agent utilities

Web Search: Ranked SERP Results JSON

web-search

Read-onlyIdempotent

Web search: ranked title/url/snippet results (Serper upstream). Use when you need live search results for a query. Not for fetching a known URL (use url-extract). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.02 Base USDC via x402.

Input Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: search query; optional n=5..10 via JSON.

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: search query; optional n=5..10 via JSON."

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.0

Behavior2/5

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

The description does add useful behavioral context beyond annotations: it discloses the free-sample/paid-URL response shape, that this call itself is not charged, and the $0.02 Base USDC x402 cost of the full result. However, it describes a live external web search (Serper upstream), which directly conflicts with the annotation openWorldHint=false; an agent relying on that annotation would misjudge whether the tool reaches outside the sandbox.

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?

Three sentences, front-loaded with purpose and routing before the commercial detail, with no filler. The payment sentence is slightly dense and parenthetical, but every clause conveys something an agent needs (free sample, pay steps, price).

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?

For a one-parameter search tool with an output schema and read-only annotations, the description covers purpose, the sibling alternative, and the x402 payment flow. Return values need not be explained because an output schema exists, so nothing essential 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?

Schema description coverage is 100% for the single query parameter, including the optional n=5..10 JSON encoding, so the schema already carries the parameter detail. The description adds no syntax or format information beyond that, which is the baseline-3 case.

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 ('Web search: ranked title/url/snippet results') plus the upstream provider (Serper), and explicitly distinguishes itself from the sibling url-extract. An agent can identify what this returns and what it is not 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?

Gives both the positive trigger ('Use when you need live search results for a query') and the exclusion with a named alternative ('Not for fetching a known URL (use url-extract)'). This is explicit when/when-not/alternative 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

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?