Skip to main content
Glama

stackexchange

by io.github.pipeworx-io

Get Answers

get_answers
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoStackExchange site slug (default: stackoverflow)
_apiKeyNoOptional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
question_idYesThe numeric question ID from the question URL

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesThe StackExchange site slug used
countYesNumber of answers returned
answersYesArray of answers to the question
question_idYesThe question ID for which answers were retrieved
quota_remainingYesRemaining API quota for this user

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "question_id": 419163
+  },
+  {
+    "question_id": 927358,
+    "site": "serverfault"
+  }
+]
  4. First observed

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The StackExchange tools are distinct, but the dominating data-lookup cluster is highly ambiguous: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, and validate_claim all route into the same underlying tool catalog. The polymorpharket tools also overlap heavily, making selection between bet_research, polymarket_edges, polymarket_arbitrage, and fill-risk checks genuinely hard.

Naming Consistency2/5

The names are all snake_case but otherwise follow no consistent pattern: bare verbs (remember, forget, subscribe), prefixed names (pipeworx_feedback, stack_get_user), composite domain names (ask_pipeworx, generate_llms_txt), and generic verbs (resolve_entity, validate_claim, search_within). The StackExchange subset itself is split between stack_get_user/stack_tags and search_questions/get_answers.

Tool Count2/5

36 tools is already in the 'too many' range for one server, and the mismatch with the server name is severe: only 5 of 36 tools relate to StackExchange. The rest form a broad Pipeworx/prediction-market data platform that would itself be oversized for a focused purpose.

Completeness2/5

For a StackExchange-focused server, the surface has core read operations but lacks question-detail-by-ID, comments, related questions, or any write/community actions, and the 31 unrelated tools do not fill that gap. For the broader apparent Pipeworx platform coverage is broad, but the set has no single coherent domain against which completeness can be meaningfully judged.

Resources