search_problems
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
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of dilemmas to return. Must be between 1 and 20. Default is 5. | |
| query | Yes | Search keywords, software name, error message, or friction topic (e.g. 'subscription price increase', 'docker desktop wsl2 memory', 'offline accounting'). Minimum 1 character. |