Skip to main content
Glama
CodexVeritax

stackoverflow-mcp-server

by CodexVeritax

search_by_error

Searches Stack Overflow for solutions to a given error message, with options to filter by language, technologies, tags, score, and accepted answers.

Instructions

Search Stack Overflow for solutions to an error message

Args:
    error_message (str): The error message to search for
    language (Optional[str]): Programming language (e.g., "python", "javascript")
    technologies (Optional[List[str]]): Related technologies (e.g., ["react", "django"])
    excluded_tags (Optional[List[str]]): Optional list of tags to exclude
    min_score (Optional[int]): Minimum score threshold for questions
    has_accepted_answer (Optional[bool]): Whether questions must have an accepted answer
    answers (Optional[int]): Minimum number of answers
    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
error_messageYes
languageNo
technologiesNo
excluded_tagsNo
min_scoreNo
has_accepted_answerNo
answersNo
include_commentsNo
response_formatNomarkdown
limitNo
Behavior3/5

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

With no annotations, the description partially covers behavior by mentioning it searches for solutions and returns formatted results. However, it does not disclose rate limits, authentication, or other potential side effects. It is adequate but not thorough.

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 concise with one purpose line followed by a parameter list. The Args/Returns structure is clear and properly front-loaded. Each line adds information without redundancy.

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 10 parameters, no output schema, and no annotations, the description adequately covers input semantics and return format. It is complete for a search tool, though it could mention result behavior (e.g., sorting).

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?

Schema description coverage is 0%, so the description carries full burden. It provides clear, meaningful descriptions for all 10 parameters (e.g., 'The error message to search for', 'Programming language'), adding value beyond the schema's bare type definitions.

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 clearly states 'Search Stack Overflow for solutions to an error message', which is a specific verb+resource combination. It distinguishes from sibling tools like search_by_query (general) and get_question (single question).

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 provides no guidance on when to use this tool versus siblings like advanced_search or analyze_stack_trace. There is no context on preferred use cases or exclusion criteria.

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