Skip to main content
Glama
CodexVeritax

stackoverflow-mcp-server

by CodexVeritax

search_by_query

Search Stack Overflow for questions matching a query, with filters for tags, score, accepted answers, and more. Returns results in JSON or Markdown.

Instructions

Search Stack Overflow for questions matching a query.

Args:
    query (str): The search query
    tags (Optional[List[str]]): Optional list of tags to filter by (e.g., ["python", "pandas"])
    excluded_tags (Optional[List[str]]): Optional list of tags to exclude
    min_score (Optional[int]): Minimum score threshold for questions
    title (Optional[str]): Text that must appear in the title
    body (Optional[str]): Text that must appear in the body
    has_accepted_answer (Optional[bool]): Whether questions must have an accepted answer
    answers (Optional[int]): Minimum number of answers
    sort_by (Optional[str]): Field to sort by (activity, creation, votes, relevance)
    include_comments (Optional[bool]): Whether to include comments in results
    response_format (Optional[str]): Format of response ("json" or "markdown")
    limit (Optional[int]): Maximum number of results to return
    ctx (Context): The context is passed automatically by the MCP

Returns:
    str: Formatted search results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
tagsNo
excluded_tagsNo
min_scoreNo
titleNo
bodyNo
has_accepted_answerNo
answersNo
sort_byNovotes
include_commentsNo
response_formatNomarkdown
limitNo
Behavior2/5

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

No annotations are provided, and the description only documents parameters and return format. It does not disclose behavioral traits such as rate limits, authentication needs, or side effects.

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?

The description is well-structured with Args and Returns sections and is front-loaded with the main purpose. However, it is somewhat lengthy due to detailed parameter documentation.

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?

Given the tool's complexity (12 parameters) and lack of output schema, the description adequately explains all inputs and return format. It covers the essential context for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing clear, concise explanations for each of the 12 parameters, including types, defaults, and purpose.

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 clearly states the tool searches Stack Overflow for questions matching a query. It specifies verb+resource, but does not differentiate from sibling tools like advanced_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lacks any guidance on when to use this tool versus alternatives. No when/when-not information is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CodexVeritax/stackoverflow-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server