Skip to main content
Glama

hackernews_search

Search Hacker News stories and comments via the keyless Algolia API to find relevant discussions by date or relevance, filtered by story, comment, show_hn, ask_hn, front page, poll, or combinations.

Instructions

Search Hacker News stories/comments via the keyless Algolia API.

sort is relevance or date. tags accepts story, comment, show_hn, ask_hn, front_page, poll or a comma-separated combination.

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

NameRequiredDescriptionDefault
sortNorelevance
tagsNostory
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one genuinely useful trait - 'keyless' (no credentials/rate-limited authenticated access required) - and 'search' implies read-only, but it says nothing about throttling, pagination, or what the results look like, leaving real gaps for a no-annotation tool.

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?

Two short sentences, purpose front-loaded, with the parameter vocabulary presented compactly. The raw inline list of tags is slightly dense but earns its place by supplying enum values the schema omits; no filler sentences.

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?

For a 4-parameter, no-annotation, no-output-schema tool, the description covers the two non-obvious parameters and the no-auth behavior. It still leaves `limit` semantics and result shape unspecified, so an agent can call it but is guessing on result volume and pagination.

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 0%, so the description must compensate and it partly does: it enumerates valid `sort` values (relevance, date) and a long list of `tags` values plus comma-combination behavior, none of which appear as enums in the schema. However, `limit` and `query` are never explained, so half the parameters still rely on inference from their names.

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?

States a specific verb and resource ('Search Hacker News stories/comments') and names the backing service ('keyless Algolia API'), which makes the scope unambiguous. It does not distinguish itself from the many sibling *_search tools (web_search, github_search, etc.), so an agent gets no explicit routing signal, but the domain is clear enough on its own.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to prefer this over web_search when the target is Hacker News, and no exclusions are given. The only contextual hint is 'keyless,' which implies no auth setup is needed, but the agent must infer the rest.

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