Tools & Toolsets
Tools are capabilities Anyy can invoke while working. A toolset is a named group of related tools selected before a model turn so the model receives a focused, policy-controlled catalog.
Browse Tools in Dashboard
Open Dashboard → Tools. The selected Profile can show:
| Category | What it contains |
|---|---|
| Built-in | Local Anyy tools and their effective governance metadata |
| MCP | Tools materialized from enabled MCP servers |
| Image | Image understanding and generation routes |
| Video | Video understanding route |
| Voice | Text-to-speech and speech-to-text routes |
| Web Search | Current-public-information search backend |
| Browser | Managed Playwright capability or a compatible MCP connection |
Select a built-in or MCP tool to inspect:
- source and toolset;
- description and input schema;
- risk class;
- approval and execution policy;
- timeout; and
- visible and stored output budgets.
The input schema is the contract Anyy uses when calling the tool. MCP definitions come from the live server catalog; control which remote tools are exposed under MCP Integration.
Built-in Default Toolsets
The default-visible groups are:
| Toolset | Typical capability |
|---|---|
artifact | List, inspect, pin, and export session files |
web | Public web search and retrieval |
sessions | Search earlier Profile sessions |
memory | Profile memory operations |
tasks, automation | Tasks, reminders, and scheduled work |
clarify | Ask structured questions when input is missing |
file, terminal | Workspace files and governed command execution |
messaging | Channel-aware messaging operations |
skills | Discover and use installed Skills |
subagents | Delegation, background work, and child controls |
tts | Spoken replies when TTS is configured |
The runtime may contain additional groups, but optional capability does not imply default visibility.
Dashboard does not provide a general “toggle every default toolset” editor. Supported feature flows update defaults coherently—for example, enabling Browser adds its toolset, and activating an MCP server can add mcp-NAME.
Tune Runtime Limits
For supported tool details, Dashboard lets you change only:
- Visible characters — maximum output projected into the conversation;
- Stored characters — maximum retained output, and never lower than the visible budget; and
- Timeout — execution limit from 100 to 600,000 milliseconds.
Saving submits a high-risk configuration ChangePlan. The values are not applied until you approve it.
Risk, approval policy, execution policy, enabled state, description, and schema are read-only in this form. Resource tuning cannot weaken the tool's security contract.
Larger output consumes more context and storage. Prefer a narrowly targeted call or a file artifact over raising every budget.
Configure Capability Backends
Dashboard capability cards guide setup and health checks:
- Web Search selects a provider, endpoint, and credential, then verifies it.
- Browser can enable a managed local Playwright service or connect to a trusted LAN endpoint.
- Media Understanding, Image Generation, and Voice & Speech use their dedicated model routes.
Follow the warnings and verification steps shown for each backend. Browser and external-service tools can have meaningful access to their environment and data.
CLI inspection and probes include:
anyy tools list
anyy tools websearch
anyy tools image --probe
anyy tools image generation --probe
anyy tools video understanding --probe
anyy tools voice tts --probe
anyy tools voice stt --probe
anyy browser status
anyy browser doctor
MCP Toolsets
Each activated MCP server has an isolated group such as mcp-docs. Its include/exclude list limits remote tools before activation. New or refreshed sessions then receive only the selected catalog.
MCP configuration does not override a tool's risk, approval, timeout, audit, or output-budget rules.
Sessions, Skills, and Visibility
A session may carry an explicit toolset selection. A Skill can request groups it needs, while the runtime still applies policy and blocks unsafe automatic additions. A child session receives only tools allowed to its parent.
When a turn contains attachments, Anyy can add the artifact group for that turn so the model can access scoped files.
A configured backend is not necessarily visible in an existing session. After enabling a capability or toolset, verify the Tools page and start a new session if the current catalog remains unchanged.
Seeing a tool does not bypass its risk, approval, ChangePlan, audit, credential, or path controls. Toolsets organize and reduce the catalog; they do not grant authority.
Troubleshooting
| Problem | Fix |
|---|---|
| Tool is listed but disabled | Check its backend and toolset configuration |
| MCP tool is missing | Probe the server, include the tool, enable and activate the toolset, then reload MCP |
| Save remains pending | Open Approvals and review the submitted ChangePlan |
| Tool output is cut off | Inspect the stored result or raise only that tool's output budget |
| Configured tool is absent in a session | Confirm its toolset is active and start a new session |
| Browser changed but tools are unavailable | Run anyy browser doctor and refresh the session |
| A child lacks a tool | The parent catalog or child policy did not allow it |
| Tool still requires approval | Approval is independent of toolset visibility |