{"version":"2.1.242","anchor":"eval-graders-can-inspect-calls-made-to-mock-tools","canonical_anchor":"eval-graders-can-inspect-calls-made-to-mock-tools","heading":"Eval graders can inspect calls made to mock tools","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/eval-graders-can-inspect-calls-made-to-mock-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Eval graders can inspect calls made to mock tools\n\nEval graders can inspect the calls that hit mock tools during a run.\n\n**What**\n\nA grader can now check the tool calls that hit mock stand-ins during an eval run. If no mocks applied, the grader gets an explicit reason instead of empty data. The note about plugins in an eval directory was also tightened.\n\n**Details**\n\n- Requires `--mocks`; without it, or when no `mocks\/` directory applies to the case, the grader is told mock stand-ins were not active in that run.\n- The eval directory note now always says the plugin is not loaded unless you name its directory, and states that naming a directory counts as consent to load it.\n- Resolving a suite path also records the directory that consent was granted for.\n\n**Evidence**\n\n`no mock stand-ins were active in this run (--mocks off, or no mocks\/ directory applies to this case)`\n\n- Area: Elsewhere\n- Names: `--mocks`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}