Skip to main content
Glama
Sign In
@isteam/hackernews-mcp

@isteam/hackernews-mcp

by isteamhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_user

Retrieve a Hacker News user's profile information including karma, about text, and account creation date by providing their username.

Instructions

Get a Hacker News user profile (karma, about, member since)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesHN username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It tells what fields the profile includes but does not mention error cases (e.g., nonexistent username) or response format. This is adequate for a simple read operation but leaves some gaps.

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?

A single concise sentence that front-loads the purpose and includes relevant detail without fluff. Every part contributes to understanding the tool.

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?

For a simple one-parameter read tool, the description is mostly complete. It explains what the tool does and what the profile contains. It could add a note about handling unknown users, but given the simplicity, it is not a significant omission.

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 schema already fully describes the only parameter 'username' with 'HN username', so schema coverage is 100%. The description adds context about the returned profile fields, but not additional parameter semantics beyond what the schema provides.

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 resource ('Hacker News user profile'), and specifies the profile contents (karma, about, member since). This distinguishes it from sibling tools like story fetchers and search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than explicitly stated. There is no direct mention of when to use this tool versus alternatives, nor any exclusions, but the focus on user profile makes the use case reasonably clear.

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