Genexxis paid agent tools (x402)

cryptonews_search

Crypto headlines of the last 72 h matching keywords or tickers (all words must match; tickers and asset names like ETH/ethereum map to tags), newest first, with corroboration count. Price: $0.003 USDC per call, paid with x402 on Base.

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": "cryptonews_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Keywords or tickers, e.g. "ethereum etf", "SOL", "stablecoin regulation"
`hours`	No	Look-back window in hours, 1-72 (default 72)
`limit`	No	Max results, 1-50 (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the time window, AND matching semantics, ticker-to-tag mapping, newest-first ordering, corroboration count, and paid x402 access. It stops short of describing error behavior, rate limits, or the exact response 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?

The description is front-loaded with the core search behavior and packs useful constraints into a compact two-sentence form. Every clause adds value, including the pricing/payment note for a paid tool.

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 three-parameter search tool with no annotations and no output schema, the description is largely complete: it covers scope, matching, ordering, and payment. It could be stronger by specifying the headline fields returned or clarifying how corroboration count is represented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: all words must match, and tickers/asset names map to tags. The "last 72 h" phrasing overlaps with the schema's default hours value but does not fully clarify how the hours parameter interacts with that default.

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?

The description clearly states a specific search operation over crypto headlines, with keyword/ticker matching. It implicitly contrasts with broad top-headlines retrieval, but it never names the sibling cryptonews_top or otherwise explicitly differentiates itself.

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 matching behavior implies when to use it for keyword or ticker searches, but there is no explicit guidance on when to choose it over cryptonews_top or other alternatives. No exclusions or prerequisites are stated.

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

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?