Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hn_show_hn

Read-onlyIdempotent

Fetch Show HN posts from Hacker News, with an optional limit, to surface new projects and launch discussions for monitoring or research.

Instructions

Get Show HN posts from Hacker News.

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_show_hn"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety and mutability are fully covered without the description. The description adds nothing beyond them: it does not say how posts are ordered, how many are returned by default, or whether results are paginated. With annotations carrying the behavior profile, this is a thin contribution.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity borders on under-specification rather than tight writing.

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?

For a low-complexity read-only feed tool with annotations covering safety and no output schema to explain, the essentials are present. Still, the undocumented optional 'limit' and the absent note on ordering/default size leave real gaps an agent would hit on first call.

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?

Schema description coverage is 0% and the single parameter 'limit' is never mentioned in the description, so neither the schema nor the prose explains its default value, maximum, or unit. A bare optional 'limit' number leaves the agent guessing about server-side caps.

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 names a specific verb and a specific resource: 'Get Show HN posts from Hacker News'. The feed name 'Show HN' is inherently differentiating from the sibling feeds hn_top_stories, hn_new_stories, hn_ask_hn, and hn_best_stories, so an agent can route correctly even though none of those siblings is named explicitly.

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?

There is no statement of when to use this feed versus hn_top_stories or hn_ask_hn, no prerequisites, and no exclusions. The agent must infer the choice purely from the tool name, which happens to be self-explanatory, but the description contributes no guidance.

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