Skip to main content
Glama

hackernews

by io.github.pipeworx-io

Get Item

get_item
Read-onlyIdempotent

Fetch a Hacker News story or comment by ID (e.g., "42153809"). Returns full text, score, author, timestamp, and child replies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe numeric Hacker News item ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoAuthor username
idYesHN item ID
urlNoItem URL
deadNoWhether item is dead/removed
kidsNoArray of child item IDs
textNoItem text content
timeNoUnix timestamp of item posting
typeNoItem type (story, comment, etc.)
scoreNoItem score/points
titleNoItem title
parentNoParent item ID
deletedNoWhether item is deleted
descendantsNoNumber of child comments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "by": {
+      "description": "Author username",
+      "type": "string"
+    },
+    "dead": {
+      "description": "Whether item is dead/removed",
+      "type": "boolean"
+    },
+    "deleted": {
+      "description": "Whether item is deleted",
+      "type": "boolean"
+    },
+    "descendants": {
+      "description": "Number of child comments",
+      "type": "number"
+    },
+    "id": {
+      "description": "HN item ID",
+      "type": "number"
+    },
+    "kids": {
+      "description": "Array of child item IDs",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "parent": {
+      "description": "Parent item ID",
+      "type": "number"
+    },
+    "score": {
+      "description": "Item score/points",
+      "type": "number"
+    },
+    "text": {
+      "description": "Item text content",
+      "type": "string"
+    },
+    "time": {
+      "description": "Unix timestamp of item posting",
+      "type": "number"
+    },
+    "title": {
+      "description": "Item title",
+      "type": "string"
+    },
+    "type": {
+      "description": "Item type (story, comment, etc.)",
+      "type": "string"
+    },
+    "url": {
+      "description": "Item URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 42153809
+  },
+  {
+    "id": 38000000
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare safe read-only behavior. The description adds valuable context by listing the returned fields (full text, score, author, timestamp, child replies), giving the agent a concrete idea of the output beyond the annotations.

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, front-loaded with the action, and includes an example and key return fields. No wasted words; every element contributes to understanding.

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?

For a simple one-parameter fetch tool with an output schema, the description is complete. It states what the tool fetches, provides an example, and lists the important return fields. Sibling tools do not require additional clarification.

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 a clear description ('The numeric Hacker News item ID'). The description adds an example and reinforces the 'by ID' usage but does not significantly extend beyond the schema's existing parameter documentation.

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's action: 'Fetch a Hacker News story or comment by ID'. It specifies the resource (Hacker News items), the scope (by ID), and provides an example ID. This distinguishes it from list-oriented siblings like 'get_stories' and 'get_top_stories'.

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 clearly conveys when to use the tool: when you have a specific item ID to fetch. It does not explicitly mention alternatives or exclusions, but the 'by ID' phrasing gives strong contextual guidance for appropriate usage.

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