Skip to main content
Glama
imprvhub

mcp-claude-hackernews

hn_best

Fetch top stories from Hacker News with customizable limits. Retrieve trending tech and startup content for insights and updates.

Instructions

Get the best stories from Hacker News

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of stories to fetch (1-50, default: 10)

Implementation Reference

  • Handler for the 'hn_best' tool: fetches best stories via HackerNewsAPI, formats them, updates lastStoriesList, and returns formatted text response.
    if (name === "hn_best") {
      const limit = typeof args?.limit === 'number' ? args.limit : 10;
      const stories = await api.getBestStories(limit);
      const formattedStories = stories.map(story => ({
        id: story.id,
        title: story.title,
        by: story.by,
        time: api.formatTime(story.time),
        url: story.url,
        score: story.score,
        commentsCount: story.kids?.length || 0
      }));
      lastStoriesList = formattedStories;
      return {
        content: [
          {
            type: "text",
            text: formatStoriesAsText(formattedStories)
          }
        ]
      };
    }
  • index.ts:178-193 (registration)
    Tool registration in listTools handler: defines name, description, and input schema for 'hn_best'.
    {
      name: "hn_best",
      description: "Get the best stories from Hacker News",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of stories to fetch (1-50, default: 10)",
            minimum: 1,
            maximum: 50,
            default: 10
          }
        }
      }
    },
  • Core helper method in HackerNewsAPI that fetches best story IDs from HN API and retrieves full story details.
    async getBestStories(limit = 50): Promise<Story[]> {
      try {
        const response = await axios.get(`${baseUrl}/beststories.json`);
        const storyIds = response.data || [];
        const storyPromises = storyIds.slice(0, limit).map((id: number) => this.getItemDetails(id));
        const stories = await Promise.all(storyPromises);
        return stories.filter((story): story is Story => story !== null && story.type === 'story');
      } catch (error) {
        console.error('Error fetching best stories:', error);
        return [];
      }
    }
  • Helper function to format the list of stories as a readable text string, used in the tool response.
    function formatStoriesAsText(stories: FormattedStory[]): string {
      if (!stories || stories.length === 0) {
        return "No stories found.";
      }
      
      return stories.map((story, index) => {
        return `${index + 1}. ${story.title}
       ID: ${story.id}
       By: ${story.by}
       Published: ${story.time}
       Score: ${story.score}
       Comments: ${story.commentsCount}
       URL: ${story.url || 'N/A'}
       ------------------------------`;
      }).join('\n\n');
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states what the tool does but doesn't disclose behavioral traits such as rate limits, authentication needs, response format, or whether it's a read-only operation. The description is minimal and lacks essential operational context.

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, efficient sentence with zero waste. It's front-loaded and directly states the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'best stories' means algorithmically, the return format, or any error conditions. For a tool with siblings and potential complexity in ranking, more context is needed for effective use.

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?

The description doesn't mention parameters at all. However, the input schema has 100% description coverage, clearly documenting the 'limit' parameter with its constraints and default. The baseline score of 3 is appropriate since the schema adequately covers parameter semantics.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('best stories from Hacker News'). It distinguishes from siblings like hn_latest and hn_top by specifying 'best stories', though the distinction between 'best' and 'top' could be ambiguous without further clarification.

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 provides no guidance on when to use this tool versus alternatives like hn_top or hn_latest. It doesn't mention any prerequisites, exclusions, or comparative contexts, leaving the agent to infer usage based solely on the tool name.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imprvhub/mcp-claude-hackernews'

If you have feedback or need assistance with the MCP directory API, please join our Discord server