We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFWhen an MCP host connects to many servers and tool definitions consume a significant portion of the context window (e.g., >1-5%), loading all upfront degrades model performance and wastes tokens.
THENImplement progressive discovery: provide a lightweight `search_tools` meta-tool that returns only tool names and one-line descriptions; let the model search; then fetch full definitions (input schema, output schema, documentation) via `get_tool_details` only when needed. Cache tool definitions host-side and refresh on `notifications/tools/list_changed`.
IFAutonomous agent sessions carry too many tools and schemas into context upfront, causing agent sprawl.
THENUse CLI mode with the instructions->inspect->run workflow. First fetch instructions, then inspect only the needed server or tool, then run a single tool. This keeps the context surface small.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site