Skip to main content
Glama
Sign In
@isteam/hackernews-mcp

@isteam/hackernews-mcp

by isteamhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ask_stories

Get Ask HN stories from Hacker News to browse community questions and discussions. Specify a limit to control how many stories are fetched.

Instructions

Get Ask HN stories

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of stories to fetch (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior itself. It only states 'Get Ask HN stories,' implying a read operation but provides no details on sorting, pagination, rate limits, or response structure. Minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with no wasted words, but it is under-specified, lacking valuable context. It is essentially a one-liner that does not fully earn its place by helping an agent decide or invoke correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity and schema coverage, a short description might suffice, but the absence of usage guidance, return value description, or behavioral notes makes it incomplete for a tool with no annotations or output schema.

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 covers 100% of the parameter (limit), so description need not add detail. The description adds no parameter-specific meaning beyond the schema, meeting the baseline for high schema coverage.

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?

Description provides a clear verb ('Get') and resource ('Ask HN stories'), which distinguishes from sibling story tools like top_stories or show_stories. However, it is terse and doesn't elaborate on scope or returned data.

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?

No guidance on when to use this tool over siblings, nor any prerequisites or exclusions. The description simply restates the function without contextualizing among related story-fetching endpoints.

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