scout-mcp

hackernews_search

Search Hacker News stories, comments, and polls via Algolia to find developer sentiment, trending tech topics, and community discussions.

Instructions

Search Hacker News (stories, comments, polls) via Algolia. Good for developer sentiment, trending tech topics, and community discussions.

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": {
      "query": "<query>"
    },
    "name": "hackernews_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query
`sort`	No	Sort order	relevance
`per_page`	No	Results per page
`tag`	No	Filter by tag: story, comment, poll, show_hn, ask_hn

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose behaviors like rate limiting, pagination limits (max 50 per_page), or that results are via Algolia (a third-party). The mention of 'via Algolia' hints at external dependency but is insufficient.

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 a single sentence that efficiently states the resource, method, and use cases with zero waste.

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?

Given no output schema and no annotations, the description is adequate for a search tool but lacks depth on result format, error handling, and authentication. It covers the core purpose but leaves gaps in behavioral context.

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 coverage is 100%, so the description adds no param-specific details. Baseline 3 is appropriate; the description cannot add value beyond schema for parameters.

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 clearly states the tool searches Hacker News stories, comments, and polls via Algolia, and distinguishes it from siblings by specifying unique use cases like developer sentiment and trending tech topics.

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?

The description implies when to use the tool (for developer sentiment, trending tech topics, community discussions) but does not explicitly state when not to use it or provide alternatives among the many sibling search tools.

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