Skip to main content
Glama

Intel hub

intel_hub
Read-onlyIdempotent

Live cross-domain intelligence hub: upcoming SpaceX launches, SpaceX/Starlink/Tesla/xAI & macro/politics RSS headlines, Hyperliquid perp funding regime & 24h movers, Polymarket/Kalshi odds, and X1 screener/canteen pulse. Not advice. $0.005 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "intel_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNooptional focus: all (default), spacex, macro, hyperliquid, or x1
paymentNoa 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.

  1. Added

TDQS

A3.9/5.0
Behavior2/5

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

The description goes well beyond the annotations by disclosing a real monetary cost ($0.005 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the two-step signing handshake, and a 'not advice' disclaimer. However, it states that 'the purchase completes inside this tool call' and that funds are charged, which conflicts with readOnlyHint=true and destructiveHint=false — spending wallet funds is not a read-only side effect. The description also never says what a call without payment returns beyond 'the terms' (HTTP 402-style payload?), leaving the first step under-specified.

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?

It is front-loaded with the content inventory, then the disclaimer, then pricing and the call flow. The opening sentence is long but every clause carries a distinct data domain; nothing reads as filler. A short list format for the domains would improve scannability slightly.

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?

With no output schema, the description compensates by enumerating the returned content categories, and it fully covers the payment prerequisite. Remaining gaps are small: no hint at response shape/size for a paid call and no statement of whether repeated paid calls are billed each time, which matters given the idempotentHint=true annotation.

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 both parameters are already documented. The description still adds meaning the schema does not: `payment` is a signed x402 payload equivalent to a PAYMENT-SIGNATURE header, and omitting it yields terms rather than data. That sequencing semantics is genuinely beyond the schema text.

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 aggregating resource and enumerates its domains concretely: SpaceX launch schedule, SpaceX/Starlink/Tesla/xAI RSS headlines, Hyperliquid perp funding and 24h movers, Polymarket/Kalshi odds, and X1 screener/canteen pulse. An agent can tell instantly that this is a multi-source market/space intel feed versus a single-domain sibling like threat_intel.

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?

It gives an explicit two-call protocol: call without `payment` to get the terms, sign with your own wallet, call again with `payment` to complete. The `topic` parameter is explained as an optional focus. What's missing is guidance on when to pick this over a narrower sibling (e.g., threat_intel) or when a single-domain call would suffice.

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.

Resources