Tools
The Tools page exposes the built-in tool catalog that ships with the platform and runtime.
Agirunner treats tools as an explicit product surface, not as hidden prompt text. Operators can inspect what exists before deciding which roles should be allowed to use which capabilities.
What Lives Here
Section titled “What Lives Here”- the built-in tool catalog
- tool categories
- distinctions between specialist-ready and orchestrator-specific tools
Why It Matters
Section titled “Why It Matters”The point of this page is not only discoverability. It is also policy. When the tool surface is explicit, the platform can reason about grants deliberately and the runtime can enforce a clearer contract.
This is one of the places where Agirunner avoids the “mystery tools” problem that shows up in many agent demos.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”The tool catalog is the source inventory, not the full assignment story.
- this page answers which built-in tools exist
- Specialists, Skills, And Models answers which specialists should be allowed to use which ones
- MCP Servers covers the external tool surfaces that complement the built-in catalog
- Runtime is where the claimed task receives the final allowed tool surface during execution
That distinction matters because Agirunner does not want tools to be implicit prompt magic. Operators can inspect the catalog, grant it deliberately, and then verify the result in live execution surfaces.