Skip to main content
Glama

hackernews

by io.github.pipeworx-io

Get Stories

get_stories
Read-onlyIdempotent

Fetch Hacker News stories of a given TYPE: top (default), new (newest), best, ask (Ask HN), show (Show HN), or job (jobs/hiring). PREFER for "newest HN stories", "top Ask HN posts", "Show HN", "HN job postings / who is hiring". Returns title, URL (or self-text for Ask/Show), score, author, comment count, and timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoStory list: top (default), new, best, ask, show, job.
countNoNumber of stories to return (default 10, max 100).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds useful behavioral details like returning self-text instead of URL for Ask/Show and listing the exact fields returned. No contradictions found.

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, front-loaded with the main action, and every clause adds value (types, usage guidance, return fields). No fluff or repetition of schema content.

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

Completeness5/5

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

The tool is simple with 0 required parameters, and the description covers return values explicitly, which compensates for the lack of an output schema. Combined with strong annotations, this is nearly complete for an agent to invoke successfully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for both parameters, so the baseline is 3. The description adds semantic clarity beyond the schema by mapping enum values to human-readable concepts ('new (newest)', 'ask (Ask HN)', 'job (jobs/hiring)'), exceeding the baseline.

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 opens with a specific verb and resource ('Fetch Hacker News stories') and enumerates the supported types. It clearly distinguishes from siblings like get_top_stories (which is likely a single fixed type) and get_hn_comments.

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 'PREFER for' phrase gives explicit user-intent examples ('newest HN stories', 'Show HN', etc.), which is strong when-to-use guidance. It does not explicitly mention when-not to use or name alternative tools, so it falls short of the top score.

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

All hackernews toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical, and deep_research also overlaps with them. The Polymarket tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also have fuzzy boundaries. An agent could easily pick the wrong meta-tool or duplicate functionality.

Naming Consistency3/5

All names are snake_case, but the pattern is mixed: some are verb_noun (get_item, list_subscriptions, resolve_entity), some are noun_noun (entity_profile, pipeworx_feedback, polymarket_edges), some are adjective_noun (deep_research, recent_alerts), and a few are single verbs (forget, recall, remember, subscribe). This is readable but not a consistent convention.

Tool Count2/5

With 36 tools, this is far too many for a server named 'hackernews'. The bulk of the tools concern Pipeworx data research, prediction markets, memory, and subscriptions — unrelated to the server's apparent purpose. Many of these could be split into separate servers, and the HN-specific functionality would be better served by a focused set of ~5-8 tools.

Completeness2/5

For the Hacker News domain implied by the server name, the surface is incomplete: there are read-only tools (search, top stories, item/comments) but no write functionality (submit, comment, vote) and no user profile access. The broader data-research capabilities are fairly comprehensive, but that does not rescue the server's coherence given its stated name.

Resources