{"version":"2.1.318","anchor":"hook-matchers-mcp-tool-name-matching-and-modelfork-effort","canonical_anchor":"hook-matchers-mcp-tool-name-matching-and-modelfork-effort","heading":"Plugins can choose the effort level for model.fork, and hook matchers match MCP tool names","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hook-matchers-mcp-tool-name-matching-and-modelfork-effort","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Plugins can choose the effort level for model.fork, and hook matchers match MCP tool names\n\nThe plugin model.fork call now takes an optional effort level and reports which one was used, and hook matchers can match full MCP tool names\n\n**What**\n\n`$.model.fork` lets a plugin ask the model a side question against the current conversation. It now takes an optional effort setting. Effort controls how much work the model puts into its answer.\n\n- `$.model.fork` now accepts `{ prompt, effort? }`. Before, it accepted only `{ prompt }`, and the prompt must still be non-empty.\n\n- `effort` must be one of the known effort levels. Any other value makes the call fail.\n\n- The call now reports which effort level was actually sent. Before, it returned only the usage figures.\n\n- Hook matchers have extra handling for MCP tools. A hook is code that runs at set points, such as before a tool is used, and a matcher decides which tools it applies to. MCP servers are outside programs that give Claude extra tools. A matcher can now match an MCP tool by its full name.\n\n**Why**\n\nPlugin authors can now pick how much effort a forked question gets, and can see which level was really used. Hook authors can target a specific MCP tool by writing its full name in a matcher.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}