/**
 * Monomind meta-tools — discovery for the (hidden-by-default) non-core roster.
 *
 * The default `tools/list` advertises only the core tool set (~80 tools) to
 * keep the per-call schema payload small. Non-core capabilities (browser,
 * github, swarm, claims, terminal, embeddings generation, etc.) remain fully
 * callable but are found through `monomind_tool_search`, which returns their
 * full inputSchema so the model can call them directly. Set
 * MONOMIND_MCP_FULL=1 to advertise the entire roster instead.
 *
 * A2: the previous `import { searchNonCoreTools } from '../mcp-client.js'`
 * was a static cycle — mcp-client.ts lazy-imports monomind-tools.ts, and
 * monomind-tools.ts statically imported back from mcp-client.ts. The runtime
 * worked because the dynamic-import side breaks the loop, but any future
 * refactor that switched to a static import on the client side would break.
 * Switched to a dynamic import inside the handler so the cycle is broken
 * on both directions.
 */
import type { MCPTool } from './types.js';
export declare const monomindTools: MCPTool[];
export default monomindTools;
//# sourceMappingURL=monomind-tools.d.ts.map