SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
MCP Tool Context Bloat
Loading too many MCP tool definitions into context bloats prompts, burns tokens, and degrades tool-selection accuracy.
In their words
agents need to know what tools are available without hardcoding lists
notion only allows one mcp connection to one project... notion eats up so much tokens, i get rate limited after a half hour
Context bar was orange before I'd typed a single thing. Tool selection was actively wrong.
Once you pass ~15–20 granular tools into Claude or whatever client you’re running: It clutters the system prompt with schemas.
adding more MCP servers/tools eventually creates more problems: tool definitions eat a lot of context, the model has more similar tools to choose between, tool selection becomes less reliable
the tool list is getting messy pretty quickly... the agent starts having too many options. Sometimes it picks the wrong one.
sessions are starting at ~100k tokens before I type anything, and roughly 70k of that is MCP tool schemas
Finding a tool that does what the boss needs based on a rough description is hard.
Now I wish they'd modularize the other 20k tokens of random tool schemas, most of which I will never use in my workflow.
I run it on 15-20 companies back to back and it starts throttling, just stops getting results
Half the time the model sends malformed arguments and there's no way to inspect what actually hit the server.
there is a chance that Qwen3.8 can ignore your MCP servers if there is a shell command it can use to complete the task
ChatGPT effectively forces you to unwrap the entire API into lots of small tools, because each one may need to be authorised separately.
This is the exact problem I'm working around right now in Claude Code, dozens of MCP servers deferred so schemas only load into context
AI agent and MCP developers
Where they talk
- r/mcp
- r/MCPservers
- r/AI_Agents
- r/LLMDevs
- r/ClaudeAI
- r/ClaudeCode
- r/LocalLLaMA
- r/LangChain
Tools they use today
- MCP
- Claude
- Claude Code
- OpenAPI
- Qwen
- Docker
- OpenCode
- ChatGPT
Why those fall short
- no layer narrows tool surface per turn; descriptions drift and are undocumented
- no way to withdraw tools from prior chat history; search still returns too many
- full tool lists injected whether used or not; no per-tool gating
- Merging moves ambiguity into argument validity; silent schema mismatches are hard to trace
- fat tools fail silently; models pick wrong branches
Map of ideas
Drawing the map…





