Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Writing an internal page about what our agents can reach and I cannot make the docs agree with themselves. The MCP tools reference is titled as the 37 tools. The MCP guide says SDODS exposes 33 to 35 tools to a role.
Which one do I put in the wiki?
Accepted answer
Neither, put a command in the wiki. But the two numbers are both right and they count different things.
no business calling run_tests; a planner does not need schedule_next.
That is why it is a range rather than a number: it depends on the role. --caps can shrink it further on top of that — the default is core,analyze,run,data,schedules, so anything under agents or issues is off unless you ask — but that is not where the 37-to-35 gap comes from.
The live answer, which is the one that will still be true next quarter:
sdods mcp -p demo-shop --caps all --list-toolsand for what a specific role gets, sdods agent review -p demo-shop --dry-run, which prints the tool list it would have used.
The number matters for one practical reason and it is worth putting in your wiki next to it: Playwright's MCP server adds about 24 more for the roles that drive a browser, and the total is what a small model chokes on. So "how many tools" is really "which profile", not trivia.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.