Skip to main content
Glama

FoxAPIs data sources

Stack Overflow question

stackoverflow_question
Read-onlyIdempotent

A Stack Overflow question: title, score, views, answer count, tags and whether it has an accepted answer, from its link. Costs 2 credits 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": {
      "url": "<url>"
    },
    "name": "stackoverflow_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://stackoverflow.com/questions/11227809/why-is-processing-a-sorted-array-faster-than-processing-an-unsorted-array"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is low. The description adds genuinely new operational context: 2 credits per call, no charge when an answer has no data, and the requirement for a FoxAPIs key — cost and auth disclosure an agent cannot get from annotations.

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?

A single dense sentence that front-loads the resource and its returned fields, followed by short cost and auth clauses. Every clause carries information; there is no filler or repetition of the title.

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 one required parameter and no output schema, the description usefully enumerates the return fields, which is the main thing an agent would otherwise lack. Cost, auth and empty-response billing are covered; only guidance on sibling selection 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?

Only one parameter, and schema coverage is 100% with a concrete example URL, so the schema already carries the semantics. The description's phrase "from its link" reinforces that the URL must point at a Stack Overflow question but adds no format or validation detail beyond the schema.

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?

States a specific resource (a Stack Overflow question) and enumerates the returned fields (title, score, views, answer count, tags, accepted-answer flag) plus the input modality ("from its link"). This makes the single-question scope distinguishable from a user or search tool, though it does not explicitly name a sibling.

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: "from its link" signals a URL-keyed lookup of one question, and the credit note hints at cost-awareness. There is no explicit when-to-use or when-not-to-use guidance relative to alternatives such as stackoverflow_user.

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