Skip to main content
Glama

stackexchange

by io.github.pipeworx-io

Stack Get User

stack_get_user
Read-onlyIdempotent

Look up a StackExchange user by numeric ID. Returns display name, reputation, badges (gold/silver/bronze counts), location, website, account age, last access, and per-site activity counts (questions/answers). Works on any StackExchange site (default: stackoverflow).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoStackExchange site slug (default: stackoverflow). Examples: serverfault, superuser, askubuntu, math, physics
_apiKeyNoOptional — a StackExchange API key (free, 10k/day) for a dedicated quota. The gateway supplies a platform key; pass your own only to override.
user_idYesThe numeric StackExchange user ID (visible in profile URL, e.g., stackoverflow.com/users/17034 → 17034)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "user_id": 17034
+  },
+  {
+    "site": "physics",
+    "user_id": 22656
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "found": {
+          "description": "User not found",
+          "enum": [
+            false
+          ],
+          "type": "boolean"
+        },
+        "hint": {
+          "description": "Explanation of why user was not found",
+          "type": "string"
+        },
+        "site": {
+          "description": "StackExchange site slug",
+          "type": "string"
+        },
+        "user_id": {
+          "description": "The user ID",
+          "type": "number"
+        }
+      },
+      "required": [
+        "site",
+        "user_id",
+        "found",
+        "hint"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "activity": {
+          "properties": {
+            "answers": {
+              "description": "Number of answers given",
+              "type": "number"
+            },
+            "down_votes": {
+              "description": "Downvotes received",
+              "type": "number"
+            },
+            "profile_views": {
+              "description": "Profile view count",
+              "type": "number"
+            },
+            "questions": {
+              "description": "Number of questions asked",
+              "type": "number"
+            },
+            "up_votes": {
+              "description": "Upvotes received",
+              "type": "number"
+            }
+          },
+          "required": [
+            "questions",
+            "answers",
+            "up_votes",
+            "down_votes",
+            "profile_views"
+          ],
+          "type": "object"
+        },
+        "badges": {
+          "properties": {
+            "bronze": {
+              "description": "Bronze badges earned",
+              "type": "number"
+            },
+            "gold": {
+              "description": "Gold badges earned",
+              "type": "number"
+            },
+            "silver": {
+              "description": "Silver badges earned",
+              "type": "number"
+            }
+          },
+          "required": [
+            "gold",
+            "silver",
+            "bronze"
+          ],
+          "type": "object"
+        },
+        "created": {
+          "description": "ISO 8601 account creation timestamp",
+          "type": "string"
+        },
+        "display_name": {
+          "description": "User's display name",
+          "type": "string"
+        },
+        "found": {
+          "description": "User was found",
+          "enum": [
+            true
+          ],
+          "type": "boolean"
+        },
+        "last_access": {
+          "description": "ISO 8601 last access timestamp",
+          "type": "string"
+        },
+        "link": {
+          "description": "URL to user's profile",
+          "type": "string"
+        },
+        "location": {
+          "description": "User's location or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "quota_remaining": {
+          "description": "Remaining API quota or null",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "reputation": {
+          "description": "User's reputation score",
+          "type": "number"
+        },
+        "site": {
+          "description": "StackExchange site slug",
+          "type": "string"
+        },
+        "user_id": {
+          "description": "The user ID",
+          "type": "number"
+        },
+        "user_type": {
+          "description": "User type (e.g., 'registered') or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "website_url": {
+          "description": "User's website URL or null",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "site",
+        "found",
+        "user_id",
+        "display_name",
+        "reputation",
+        "badges",
+        "location",
+        "website_url",
+        "link",
+        "user_type",
+        "activity",
+        "created",
+        "last_access",
+        "quota_remaining"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds behavioral context by specifying return fields and cross-site support, which goes beyond the annotations without contradicting them.

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 sentences, front-loaded with the action and return fields, and contains no redundant or vague wording.

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?

The tool has a rich output schema and clear annotations, and the description covers purpose, return values, and site flexibility. A minor gap is not explicitly warning that user IDs are site-specific, though the schema's URL example implies this.

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 has 100% description coverage for parameters, so the baseline is 3. The description reinforces the numeric ID and default site, but adds no new parameter semantics beyond what the schema already provides.

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 begins with 'Look up a StackExchange user by numeric ID,' providing a specific verb, resource, and method. It also lists the return fields and clarifies that it works on any StackExchange site, distinguishing it from sibling tools like get_answers or search_questions.

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 clearly implies when to use the tool — when you have a numeric StackExchange user ID and need profile information. It also mentions the default site, but it does not explicitly state alternatives or when not to use it, so it falls short of a 5.

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