Skip to main content
Glama

search_problems

Read-onlyIdempotent

Search SaidItHere for real-world software dilemmas, framework gotchas, tool fatigue, and battle-tested community consensus workarounds from Reddit, Hacker News, GitHub, and Stack Overflow.

Usage Guidelines:

  • Primary discovery tool: use FIRST when investigating bugs, library gotchas, unexpected price hikes, or developer complaints by keywords.

  • Sibling routing: follow up with 'get_problem(slug)' using the discovered dilemma slug to inspect full evidence quotes, sources, and step-by-step workarounds.

  • Sibling routing: if 0 matching dilemmas are returned, use 'suggest_dilemma' to queue the topic for crawler consensus synthesis.

  • Do NOT use for generic language syntax lookups or textbook documentation queries.

Behavior & Side Effects:

  • Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.

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_problems"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of dilemmas to return. Must be between 1 and 20. Default is 5.
queryYesSearch keywords, software name, error message, or friction topic (e.g. 'subscription price increase', 'docker desktop wsl2 memory', 'offline accounting'). Minimum 1 character.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of dilemmas to return (default: 5, max: 20)"New value: +"Maximum number of dilemmas to return. Must be between 1 and 20. Default is 5."
    • addedInput schema / properties / limit / maximum
      Added value: +20
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / query / description
      Previous value: -"Search keywords, software name, error message, or friction topic (e.g. 'subscription price increase', 'docker desktop wsl2 memory')"New value: +"Search keywords, software name, error message, or friction topic (e.g. 'subscription price increase', 'docker desktop wsl2 memory', 'offline accounting'). Minimum 1 character."
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

While annotations confirm safety, the description goes further by explicitly stating that it is 'pure read-only' and 'without side effects,' detailing that it 'Does not modify user, session, or database state.' This high level of behavioral assurance is excellent behavioral transparency.

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?

The information is structured logically (Introduction, Usage, Behavior) and every sentence is highly informative. While lengthy, the length is entirely justified by the necessity of explaining the discovery workflow and necessary exclusions.

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?

Given its role as the primary entry point to a complex knowledge base, the tool is maximally complete. It outlines the entire workflow, from the initial search to the required use of related sibling tools (`get_problem` and `suggest_dilemma`) upon successful or unsuccessful discovery.

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?

Although the schema is 100% covered, the description adds significant value by guiding the user on semantic query composition. It provides concrete examples of effective search strings (e.g., 'subscription price increase', 'docker desktop wsl2 memory'), teaching the agent *how* to use the parameters effectively.

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 specifies the exact domain of search ('real-world software dilemmas, framework gotchas') and clearly identifies the resource being searched ('SaidItHere'). It distinguishes its function from related tools by explaining its purpose as a discovery tool, contrasting it with the function of get_problem.

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

Usage Guidelines5/5

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

It provides a comprehensive usage guide, explicitly defining when to use the tool ('Primary discovery tool' for bugs or price hikes). It also includes crucial negative guidelines, stating what the tool should *not* be used for ('generic language syntax lookups or textbook documentation queries').

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