SiteCheck Agent Intel & Dev

Keyword discussion velocity on Hacker News: stories

agent_intel_social_signal_aggregator

Read-only

Keyword discussion velocity on Hacker News (Algolia HN Search, public): stories in the last 24 hours, stories in the last 7 days, velocity (24h count vs. 7-day daily average) and the top 24h stories with points and comments. Only Hacker News: Reddit and Bluesky blocked automated requests in testing, and no sentiment score is given. Price: $0.003 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "keyword": "<keyword>"
    },
    "name": "agent_intel_social_signal_aggregator"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	Keyword or short phrase, 2 to 80 characters

Output Schema

Name	Required	Description	Default
`last7d`	No
`source`	No
`keyword`	No
`last24h`	No
`velocity`	No
`checkedAt`	No
`topStories24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not responsible for basic safety disclosure. It adds meaningful context beyond annotations: only HN is queried, no sentiment score is returned, and pricing is $0.003 per successful call via x402 with failed calls uncharged. It does not cover rate limits or auth details.

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?

The description front-loads the topic and source, then covers returned metrics, scope exclusions, and pricing. It is dense and somewhat run-on but contains no obvious 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?

The tool has an output schema and clear annotations, and the description adds scope limits, output shape at a high level, lack of sentiment scoring, and payment behavior. It is nearly complete for a one-parameter read-only tool, with the main omission being explicit sibling routing guidance.

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 single keyword parameter is already documented with its 2–80 character constraint. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 names a specific resource (Hacker News stories) and concrete metrics (24h/7d counts, velocity, top 24h stories with points and comments). It does not explicitly distinguish this from sibling tools such as agent_intel_news_radar or agent_intel_viral_trending_radar, so it falls short of a 5.

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 description bounds usage with 'Only Hacker News' and notes that Reddit and Bluesky blocked automated requests, which implicitly narrows when the tool is appropriate. However, it does not explicitly say when to choose this over sibling news/trend tools or what alternative to use for sentiment or multi-platform social data.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?