Skip to main content
Glama

hn_search

Read-only

Search Hacker News stories by keyword to retrieve titles, points, comment counts, links, and HN IDs, ordered by relevance.

Instructions

Search Hacker News stories by keyword. Returns title, points, comment count, link and HN id, most relevant first.

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": "hn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many stories (1-20)
queryYesWhat to search for, e.g. 'MCP server'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and external-source behavior are covered. The description usefully adds the result ordering and returned fields, but says nothing about pagination limits or what happens with no matches.

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?

Two sentences with no wasted wording; the core action is front-loaded and the return shape follows immediately.

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, describing the returned fields is a meaningful contribution, and the low-complexity two-parameter surface is well covered. The only real gap is the absence of guidance relative to the sibling hn_story tool.

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%, with both query and limit documented in-schema including the 1-20 range and a sample query. The description adds no meaning beyond that, so baseline 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 states a specific verb and resource ("Search Hacker News stories by keyword") and identifies the ranking (most relevant first). It stops short of distinguishing this from the sibling hn_story, which presumably fetches one story by id, so an agent must infer the split.

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?

Keyword search implies the when-to-use condition, but there is no explicit statement of when to prefer hn_story or when not to use this tool. Usage is implied rather than stated, which is the minimum viable level.

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

Deploy Server

Other Tools