Skip to main content
Glama

hn-mcp-server

by io.github.cyanheads

Hn Get User

hn_get_user
Read-only

Get an HN user profile with karma, about, and optionally their most recent submissions resolved into full items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesHN username. Case-sensitive. Trimmed; blank or whitespace-only input is rejected.
submissionCountNoPage size — how many submissions to resolve per call. Only used when includeSubmissions is true.
submissionOffsetNoHow many submissions to skip before resolving, counting back from the most recent. Use with submissionCount to page through a long history: request offset 0, then offset submissionCount, and so on. The enrichment block echoes submissionOffset and, when more remain, the offset to send next. Only used when includeSubmissions is true.
includeSubmissionsNoResolve the user's most recent submissions into full items. Without this, only the submission count is available.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe submissionCount cap that was applied.
userNoUser profile.
errorNoPresent when the call failed. Absent on success.
shownNoNumber of submissions returned.
noticeNoPagination context — which window of the history this page covers and the submissionOffset to send next, or a warning that the offset is past the end. Absent when the page reaches the end of the history, or when no submissions were resolved.
truncatedNoTrue when submissions remain beyond this page.
submissionsNoOne page of submissions, most recent first, starting at submissionOffset. Absent when includeSubmissions is false or the user has never submitted. Empty when the page holds no live items — either the offset is past the end, or every item in the window was deleted or flagged.
submissionOffsetNoThe offset this page started at. Absent when includeSubmissions is false or the user has never submitted.

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, so the description doesn't need to repeat it. The description adds the behavioral detail that submissions are resolved into full items, which implies extra fetching. However, it does not disclose other behavioral traits like pagination limits or error handling beyond what the schema already provides. Thus it adds some context but not extensive.

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, compact sentence that front-loads the primary action and resource, then mentions the key fields and optional feature. There is no redundancy or filler; every element earns its place, 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.

Completeness4/5

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

The description covers the core functionality and the optional submission resolution, which is the main distinguishing feature. The schema fully documents parameters, and the annotation declares read-only behavior. While it doesn't list every possible returned field, the presence of an output schema handles that. Overall, the description is sufficiently complete for a tool of moderate complexity.

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?

All four parameters have detailed descriptions in the input schema, including case-sensitivity, pagination, and conditional usage. The tool description adds no additional parameter-specific meaning; it only summarizes what the schema already states. With 100% schema coverage, the baseline of 3 is appropriate.

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 action (Get) and the target resource (HN user profile), and specifies the key contents (karma, about) and an optional behavior (resolving submissions). This distinctively separates it from sibling tools that focus on stories, threads, or search, making its purpose unambiguous.

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 indicates the tool is for fetching user profiles, and the sibling names (hn_get_stories, hn_get_thread, hn_search_content) make it obvious this is the user-specific tool. However, it does not explicitly state when to prefer this over alternatives or list exclusions, so it stops short of full explicit guidance.

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

All hn-mcp-server 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

A4.1/5.0
Disambiguation5/5

Each tool targets a clearly distinct resource: feed stories, threaded items, user profiles, and content search. No overlap exists; an agent can easily select the appropriate tool for a given intent.

Naming Consistency5/5

All tools follow a uniform `hn_` prefix with a consistent verb_noun pattern (`get_stories`, `get_thread`, `get_user`, `search_content`). The naming is intuitive and predictable.

Tool Count5/5

Four tools is well-scoped for a Hacker News read-only server, covering core data access patterns without redundancy. Each tool earns its place, and the count is neither too thin nor bloated.

Completeness4/5

The surface covers fetching stories, retrieving item trees, viewing user profiles, and searching content. Minor gaps exist (e.g., no direct way to list a user's comments, no explicit single-item fetch beyond depth-0 thread), but agents can work around them using the thread tool.

Resources