Skip to main content
Glama

Web Scraper Markdown Reader, Live Search & Agent Pass x402 MCP

Live Multi-Source Web, News & GitHub Search ($0.02 USDC via x402)

search_live_web_x402
Read-onlyIdempotent

Searches live News, HackerNews, GitHub, and Wikipedia in parallel ($0.02 USDC on Base via x402 or 30d Pass).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_live_web_x402"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the description's job is to add access context — and it does, disclosing that calls cost $0.02 USDC on Base via x402 or are covered by a 30d Pass. It stops short of describing latency, rate limits, or result shape.

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?

A single front-loaded sentence that names the sources first and the payment model second, with zero filler. Every clause carries information.

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?

For a one-parameter, annotation-rich search tool, the definition covers sources, execution model, and payment requirements — enough to call it correctly. The main omission is any hint about result volume or how to choose it over the single-page scrape siblings.

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?

Only one parameter (query) exists and the schema already documents it at 100% coverage, so the description cannot add much. It adds nothing about query syntax, operators, or result limits beyond the schema's 'Search keywords'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (searches) and enumerates the resources covered (News, HackerNews, GitHub, Wikipedia) with the parallel-execution behavior made explicit. It contrasts implicitly with the scrape/preview siblings by being multi-source, though it never names them.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as scrape_webpage_markdown_x402 for single pages. The agent must infer that a broad multi-source query belongs here rather than a targeted URL fetch.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.