Stackexchange

Get Answers

get_answers

Read-onlyIdempotent

Get answers for a specific StackExchange question by ID. Returns answer body, score, and whether it is accepted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question_id": 419163
    },
    "name": "get_answers"
  }
}

Input Schema

Name	Required	Description
`site`	No	StackExchange site slug (default: stackoverflow)
`_apiKey`	No	Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
`question_id`	Yes	The numeric question ID from the question URL

Output Schema

Name	Required	Description
`site`	Yes	The StackExchange site slug used
`count`	Yes	Number of answers returned
`answers`	Yes	Array of answers to the question
`question_id`	Yes	The question ID for which answers were retrieved
`quota_remaining`	Yes	Remaining API quota for this user

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 18, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Optional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.",
+  "type": "string"
+}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "answers": {
+      "description": "Array of answers to the question",
+      "items": {
+        "properties": {
+          "answer_id": {
+            "description": "Unique answer identifier",
+            "type": "number"
+          },
+          "body": {
+            "description": "Answer body HTML content",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created": {
+            "description": "ISO 8601 creation timestamp",
+            "type": "string"
+          },
+          "is_accepted": {
+            "description": "Whether this is the accepted answer",
+            "type": "boolean"
+          },
+          "last_activity": {
+            "description": "ISO 8601 last activity timestamp",
+            "type": "string"
+          },
+          "owner_name": {
+            "description": "Display name of the answer author",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "owner_reputation": {
+            "description": "Reputation score of the answer author",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "score": {
+            "description": "Answer score (votes)",
+            "type": "number"
+          }
+        },
+        "required": [
+          "answer_id",
+          "body",
+          "score",
+          "is_accepted",
+          "owner_name",
+          "owner_reputation",
+          "created",
+          "last_activity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of answers returned",
+      "type": "number"
+    },
+    "question_id": {
+      "description": "The question ID for which answers were retrieved",
+      "type": "number"
+    },
+    "quota_remaining": {
+      "description": "Remaining API quota for this user",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "site": {
+      "description": "The StackExchange site slug used",
+      "type": "string"
+    }
+  },
+  "required": [
+    "site",
+    "question_id",
+    "count",
+    "quota_remaining",
+    "answers"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "question_id": 419163
+  },
+  {
+    "question_id": 927358,
+    "site": "serverfault"
+  }
+]

First observedApr 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by listing the returned fields (body, score, accepted), which goes beyond the structured annotations.

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 two concise sentences, the first stating the core purpose and the second summarizing the returned data. It is front-loaded and every word adds value, with no redundancy.

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?

This is a simple read-only tool with complete schema coverage and an output schema present. The description covers purpose and key return fields, which is sufficient for the tool's complexity. It could mention error cases or rate limits, but these are not critical given the annotations and schema.

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 input schema descriptions cover all three parameters (100% coverage), so the schema already provides the necessary meaning. The description's 'by ID' adds no semantic value beyond the schema's explanation of question_id, so the baseline 3 applies.

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 tool fetches answers for a specific StackExchange question by ID. The verb 'Get' plus the resource 'answers' and the scoping 'specific question by ID' make the purpose unambiguous and distinguish it from sibling search tools.

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 implies usage when the user already has a question ID, providing clear context. However, it does not explicitly exclude alternatives or mention when to use e.g. search_questions to first find an ID, so it falls short of full guidance.

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

All Stackexchange tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.