Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Hacker News comment context

hackernews_comment_context_get
Read-onlyIdempotent

Fetch a Hacker News comment with its full ancestor chain to the root story so you can understand the discussion context behind a specific comment.

Instructions

Get a Hacker News comment with its ancestor chain to the root story. Requires id.

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "hackernews_comment_context_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHacker News comment id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that the result is a chain back to the root story, but says nothing about depth limits, truncation, ordering, or that the analytics params are mandatory on every call.

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?

Two short sentences with the core capability front-loaded and no filler. The trailing "Requires `id`" mildly duplicates the schema's required list but is harmless.

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 read-only lookup with no output schema, the description does tell the agent what comes back (comment plus ancestor chain). It is still thin on retrieval behavior — how deep the chain goes, whether it can be truncated, and how large a response to expect — which matters for planning a call.

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?

Schema description coverage is 100%, so all four parameters (id, context, llm_model, conversation_id) are already documented in detail. The description only restates that `id` is required and adds no format, range, or semantics beyond the schema; baseline 3 applies.

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?

States a specific verb (Get), resource (Hacker News comment), and a distinguishing scope: the ancestor chain up to the root story. That scope separates it in spirit from hackernews_item_get and hackernews_story_comments_list, though no sibling 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 Guidelines3/5

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

Usage is only implied by the returned shape (comment plus ancestors), which tells an agent this is the right call when parent-chain context matters. There is no explicit when-to-use/when-not guidance and no named alternative for fetching a bare comment or a full comment list.

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