Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
hn_searchA

Search Hacker News stories by keyword. Returns title, points, comment count, link and HN id, most relevant first.

hn_storyA

Get one Hacker News story by id: title, author, score, link, text and comment count.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: hn_search is keyword-based discovery, while hn_story is a direct fetch by id. An agent can easily choose between them based on whether it has an id or a query.

Naming Consistency5/5

Both tools use the same hn_ prefix followed by a short noun/verb (search, story). The pattern is predictable and consistent.

Tool Count2/5

Two tools is very thin for a Hacker News integration; only keyword search and single-story fetch are exposed. Whole categories of common operations are absent, making the surface feel under-scoped.

Completeness2/5

Core reading is covered (search + fetch a story), but there is no way to retrieve comments, list top/new/best stories, or look up users. These are significant gaps for the stated Hacker News domain, leaving agents with dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues