Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_web_research

Search HackerNews, GitHub, arXiv, and Wikipedia in one paid x402 API call to gather research and news without managing API keys.

Instructions

Paid x402 API ($0.004 USDC on Base): Universal multi-source research & news search across HackerNews, GitHub Repositories, arXiv papers, and Wikipedia with zero API keys (60s cache).

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": {
      "q": "<q>"
    },
    "name": "verifystack_web_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query (2-200 characters)
limitNoMax items per source (1-15, default 5)
sourcesNoComma-separated: hackernews, github, arxiv, wikipedia, or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantially well: it discloses that this is a paid x402 endpoint costing $0.004 USDC on Base, that no API keys are needed, and that responses are cached for 60s. It omits failure behavior (what happens on payment failure or rate limiting) and says nothing about the shape of the returned results.

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?

A single dense sentence with no filler. The pricing and protocol details lead before the actual purpose, which slightly buries what the tool does for an agent skimming the first few words, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter paid search tool with no output schema, the cost, payment rail, cache window, and keyless access are all covered. The missing piece is what a result looks like (fields, per-source grouping, or merged ranking), which the agent cannot infer from an absent output schema.

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%, and the schema already documents the query length bounds, the 1-15 range with default 5 for `limit`, and the accepted `sources` values. The description adds no syntax, precedence, or semantics beyond restating the source list, 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?

The description names a specific operation and resource: multi-source research and news search across four explicitly listed sources (HackerNews, GitHub, arXiv, Wikipedia). No sibling tool performs a general research/news search, so the agent can route to it on the basis of the description alone.

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?

Usage is only implied by the phrase 'universal multi-source research & news search'. There is no statement of when to prefer this over the sibling tools, no exclusions, and no note about when narrowing the `sources` argument is preferable to passing 'all'.

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