Skip to main content
Glama

stackexchange_search

Read-onlyIdempotent

Search Stack Exchange sites for questions using a query, with optional site and page parameters to target results.

Instructions

Search Stack Exchange (default: Stack Overflow) for questions.

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": "stackexchange_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
siteNoSE site (default: stackoverflow).
queryYesSearch query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description carries a reduced burden. The only content it adds is the default site, which is already stated in the schema, and it says nothing about result volume, ordering, or pagination behavior.

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?

A single short sentence with the resource and the default scope front-loaded; nothing is wasted and nothing needs to be scanned for.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter search tool with full schema coverage and a safety-covered annotation set is mostly specified. However, with no output schema there is no indication of what a result contains (titles, IDs, links) or how the page parameter behaves, leaving follow-up calls such as stackexchange_question to guesswork.

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%, so query, site and page are all documented in the structured schema. The description's "default: Stack Overflow" merely repeats the site parameter default, adding no syntax, format, or page-size meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ("Search Stack Exchange ... for questions") and adds the default site, so an agent knows exactly what it does. It does not distinguish this from the sibling stackexchange_question, so it stops short of 5.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the sibling stackexchange_question, which is the obvious alternative when the target question ID is already known. Usage context is only implied by the word "Search" in the name.

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

Deploy Server

Other Tools