Skip to main content
Glama

webbersites-x402-data-api

by io.github.webberdesign

post_search

WEB SEARCH for keyless agents — POST {query} and get LLM-ready results: title, url, extracted content snippet, relevance score, plus a direct answer synthesized from live results. Options: max_results (1-10, default 5), topic (general|news). No API key, no account — the x402 payment IS the auth. Query up to 400 chars. ($0.01 per call, paid via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query, up to 400 characters
topicNogeneral (default) or news
max_resultsNoHow many results to return (1-10, default 5)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
answerNodirect answer synthesized from the live results
resultsNoranked results: {title, url, content, score}

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Discloses cost ($0.01 per call), auth mechanism (x402), query length limit, and result format, going beyond the annotations. No clear contradiction with annotations, though readOnlyHint=false may be due to payment side effect.

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?

Description is two sentences with key information front-loaded. Slightly dense but efficient; could be broken for readability.

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?

Covers all relevant aspects: purpose, parameters, return format, cost, and constraints. Given the output schema exists, description provides sufficient context for an agent to use the 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%, so description adds marginal value by restating parameters. No additional semantic depth beyond schema descriptions.

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 clearly states it performs a WEB SEARCH for keyless agents, returning LLM-ready results. It distinguishes from siblings by specifying it's a POST-based search tool.

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

Usage Guidelines3/5

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

The description implies usage for web search without API key, but does not explicitly compare with alternative search or data retrieval tools among siblings like get_scrape or get_summarize.

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

All webbersites-x402-data-api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but the SEO-related tools (head_check, full_audit, site_audit, etc.) overlap in scope, potentially causing confusion despite clear descriptions.

Naming Consistency5/5

Tool names consistently follow a get_/post_/delete_ verb pattern with descriptive noun phrases (e.g., get_seo_head_check, post_store_collection), with no mixing of naming conventions.

Tool Count2/5

With 46 tools covering a wide breadth of domains (SEO, accessibility, music, crypto, linting, etc.), the count is excessive for a single server, feeling unfocused and heavy.

Completeness4/5

The tool set covers most core operations for each sub-domain, but minor gaps exist (e.g., missing update for datastore, limited music operations).

Resources