Skip to main content
Glama
Sign In
Hacker News MCP Server

Hacker News MCP Server

by fritzprix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Get Updates

hn_get_updates
Read-onlyIdempotent

Retrieve IDs of recently updated Hacker News items and user profiles to track changes.

Instructions

Retrieve recently updated item and profile IDs.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that it retrieves IDs, but does not disclose additional behavioral traits such as update frequency or pagination. No contradiction with annotations.

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?

The description is a single sentence, well-suited for a simple tool. It is front-loaded with the key action and resource. However, it lacks any structural elements like bullet points or examples.

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?

The tool has one optional parameter and no output schema. The description omits important context about what 'recently updated' means (e.g., since last call, within a time window). This could lead to confusion.

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

Parameters2/5

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

With 0% schema description coverage, the description should explain the single parameter response_format. It does not mention it at all, leaving the agent without guidance on valid values or defaults.

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 uses a specific verb ('retrieve') and identifies the resource ('recently updated item and profile IDs'). It clearly distinguishes from sibling tools that fetch specific story lists or individual items.

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?

The description does not provide any guidance on when to use this tool versus alternatives like hn_get_new_stories. There is no mention of use cases, prerequisites, or exclusions.

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