Skip to main content
Glama
stackexchange-mcp

stackexchange-mcp

by YashLimbani

search_questions

Read-onlyIdempotent

Search Stack Overflow or another Stack Exchange site for existing discussions on a topic. Returns question summaries with title, score, tags, and link so you can find solutions without reading full text.

Instructions

Search Stack Overflow (or another Stack Exchange site) for questions about a topic.

Use this to find existing discussions and solutions. It returns short summaries (title, score, tags, link), not full text. To read a question and its answers, pass a question_id from the results to get_question.

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": {
      "query": "<query>"
    },
    "name": "search_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site slug, e.g. 'stackoverflow' or 'serverfault'.stackoverflow
sortNoResult order. 'votes' favors well-regarded questions.relevance
tagsNoOptional tags to restrict results, e.g. ['python', 'asyncio'] (max 5).
limitNoNumber of results to return.
queryYesKeywords to search for, e.g. 'asyncio sleep vs time.sleep'.
accepted_onlyNoOnly return questions that have an accepted answer.

Output Schema

NameRequiredDescriptionDefault
noteNo
resultsYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/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 profile is covered. The description adds value beyond them by disclosing the result shape (short summaries with title, score, tags, link, not full text), which tells the agent to expect truncated content. It omits any mention of quota/rate limits, notable given a get_quota_status sibling exists.

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?

Three short sentences with no filler: purpose first, usage second, follow-up routing third. The key constraint (summaries, not full text) is front-loaded rather than buried, and nothing is repeated from the schema or annotations.

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?

For a six-parameter search tool with an output schema and full annotation coverage, the definition supplies what it must: what is searched, what comes back, and where to go next. The only meaningful omission is any hint about quota/rate limits, which the presence of get_quota_status suggests an agent may need to know about.

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 description coverage is 100%, and every parameter (site, sort, tags, limit, query, accepted_only) is documented in the schema itself, so the schema carries the semantics. The description adds no parameter-level detail such as query syntax or tag behavior, which is the expected baseline of 3 when coverage is this high.

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 names a specific verb and resource ("Search Stack Overflow (or another Stack Exchange site) for questions") and immediately contrasts itself with get_question by stating it returns short summaries (title, score, tags, link) rather than full text. An agent can distinguish it from the read-one-question sibling without consulting either schema.

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?

It gives clear when-to-use guidance ("Use this to find existing discussions and solutions") and an explicit handoff rule: pass a question_id from the results to get_question for full text. It does not address when to prefer the other search entrypoint (search_by_error_message) or when a search would be futile, so it stops short of explicit exclusions.

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