apex-x1

crypto_news

Crypto news from 8 newsrooms (CoinDesk, Cointelegraph, Decrypt, The Block, Bitcoin Magazine, The Defiant, Blockworks, Bitcoin.com) in one call, newest first, with the coins each story names. Filter by coin, text or since. $0.001 per call over x402 (USDC on Base only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	only stories containing this text
`coin`	No	only stories naming this coin, e.g. BTC
`limit`	No	how many stories, 1-100 (default 30)
`since`	No	only stories published after this time (ISO or unix seconds)
`payment`	No	a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

addedInput schema / properties / coin

Added value: +{
+  "description": "only stories naming this coin, e.g. BTC",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "how many stories, 1-100 (default 30)",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "only stories containing this text",
+  "type": "string"
+}

addedInput schema / properties / since

Added value: +{
+  "description": "only stories published after this time (ISO or unix seconds)",
+  "type": "string"
+}

AddedSep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Without annotations, the description carries the burden and does well: it discloses cost ($0.001/call), the payment rail (USDC on Base only), and the exact multi-call negotiation flow, which an agent could not infer from structured fields. It omits failure behavior (what happens if payment is unsigned/expired) and pagination limits.

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 dense sentences, front-loaded with what the tool returns and how to pay; the payment instructions are essential, not filler. Slightly packed with parenthetical detail but nothing is wasted.

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 paid, no-output-schema, no-annotation tool, the description covers the essentials: content, filters, ordering, cost, and the payment handshake. Gaps are minor (rate limits, retry/expiry behavior) and unlikely to block a correct call.

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%, so all five parameters are already documented there; the description only restates the filters (coin, text, since) at a high level without adding syntax or default nuance beyond the schema's own limit default of 30.

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 resource (crypto news), scope (8 named newsrooms in one call), ordering (newest first), and enrichment (coins each story names). An agent can immediately tell this apart from social_feed or research_search.

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

Usage Guidelines4/5

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

Gives concrete filter options (coin, text, since) and a clear two-step payment protocol: call once without `payment` for terms, sign, call again with payment. It does not, however, name a sibling alternative or state when NOT to use this tool.

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

All apex-x1 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?