Skip to main content
Glama

FoxAPIs data sources

Stack Overflow user

stackoverflow_user
Read-onlyIdempotent

A Stack Overflow profile by numeric user id: reputation, badges, answers and questions counts. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "user_id": "<user_id>"
    },
    "name": "stackoverflow_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesFor example: "22656"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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. The description goes beyond them with two genuinely useful facts the annotations cannot express: the billing model (1 credit per call, not charged when an answer has no data) and the FoxAPIs key requirement.

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?

Three short sentences with the resource and returned fields front-loaded, followed by cost and auth notes. No filler; each sentence contributes something, though the cost/auth clause could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description supplies the field list that would otherwise be missing, plus cost and authentication requirements. Nothing an agent needs to call this correctly is absent.

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 coverage is 100% for the single user_id parameter, including the example "22656", so the schema already carries the semantics. The phrase 'numeric user id' reinforces that the string parameter holds digits, but adds no format, range, or lookup guidance beyond what the schema shows. 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?

The description states a specific resource (a Stack Overflow profile) keyed by numeric user id and enumerates the fields returned: reputation, badges, answers and questions counts. That is enough to distinguish it from a question-level sibling like stackoverflow_question, 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 implied rather than stated: 'by numeric user id' tells the agent the expected identifier, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to the sibling tool for question-level lookups. An agent can infer the use case but gets no routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources