Skip to main content
Glama

Search Stack Overflow questions and accepted answers

stackoverflow
Read-only

Stack Overflow questions matching words, optionally by tags and accepted status: title, score, answer count, accepted flag, tags and link. With answers=1 the accepted answer's first 600 characters are included. Content is CC BY-SA 4.0 (attribution per item). Stack Exchange API 2.3. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "stackoverflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words
limitNo1 to 20 (default 5)
taggedNoTags separated by commas, e.g. rust,tokio
answersNo1 to include the accepted answer's text
acceptedNotrue to keep only questions with an accepted answer

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
checkedAtNo
questionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses pricing ($0.002 per successful call), payment rail (x402 USDC on Base and other networks), that failed calls are not charged, API version, license/attribution obligations, and the 600-character truncation of included answers.

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?

Front-loads the core purpose and result fields, then handles answer inclusion, licensing, and cost in compact sentences. Dense but each sentence carries distinct information with little waste.

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?

With an output schema present, return values need no explanation; the description still covers the key behavioral concerns an agent needs—pricing, payment mechanism, licensing/attribution, and answer truncation—leaving nothing material missing.

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%, so the schema already documents q, limit, tagged, answers and accepted. The description adds only the answers=1 truncation detail, which the schema omits; the rest repeats what the schema covers.

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?

States a specific verb and resource (search Stack Overflow questions) and enumerates the returned fields plus the answers=1 behavior, clearly distinguishing it from sibling search tools for other sources.

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?

Says to provide search words, optional tags and accepted status, but gives no explicit when-to-use vs. when-not or comparison to alternative search tools. Usage is implied by the parameter descriptions rather than spelled out.

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