Skip to main content
Glama
stackexchange-mcp

stackexchange-mcp

by YashLimbani

get_question

Read-onlyIdempotent

Retrieve a Stack Exchange question and its top answers as Markdown, with author, link, and license details for citing debugging help.

Instructions

Read one question in full, together with its best answers.

The question and answer bodies are returned as Markdown with code blocks preserved. Long posts are truncated and end with a link to the full text. Each item includes its author, link and license, so cite them when you use the content.

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": {
      "question_id": "<question_id>"
    },
    "name": "get_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite slug the question belongs to, e.g. 'stackoverflow'.stackoverflow
max_answersNoHow many answers to include (accepted answer first, then by votes). Use 0 for the question only.
question_idYesQuestion ID, from search_questions results.

Output Schema

NameRequiredDescriptionDefault
bodyYes
linkYes
tagsYes
scoreYes
titleYes
authorYes
answersYes
createdYes
licenseYes
view_countYes
question_idYes
answer_countYes
last_activityYes
answers_not_shownYes
has_accepted_answerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. Beyond that, the description adds real behavioral context: Markdown with code blocks preserved, truncation of long posts with a link to the full text, and a per-item license/author citation obligation. It stops short of describing answer ordering or error behavior, which keeps it from a 5.

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 purpose is front-loaded in a single sentence, followed by exactly the operational details that matter (format, truncation, attribution). No sentence is filler.

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?

With full annotation coverage, 100% schema description coverage, and an output schema, the remaining burden is behavioral, and the description covers format, truncation, and citation. The missing piece is guidance on when to reach for this versus search_questions.

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% and the schema already documents site slugs, the max_answers 0–5 range with 'accepted answer first, then by votes', and the question_id origin. The description adds nothing beyond 'best answers', so the baseline 3 is appropriate.

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 first sentence gives a specific verb and resource: read ONE question in full plus its best answers. 'One question in full' implicitly contrasts with the search_questions sibling, but no sibling is named, so an agent must infer the distinction between fetch-detail 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 Guidelines2/5

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

The description offers no when-to-use or when-not guidance, and no alternative is named. The only routing clue ('Question ID, from search_questions results') lives in the parameter schema, not the description text.

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