Tools
Tools are the capabilities Anyy can invoke while working: built-in operations, MCP tools, web search and media backends.
Open Dashboard → Tools to see what the selected Profile can expose to sessions.
Tool categories
| Category | What you manage |
|---|---|
| Built-in | Local tool definitions and Codemode settings |
| MCP | Tools currently materialized from enabled MCP servers |
| Image | Image understanding and generation model routes |
| Video | Video understanding model route |
| Voice | Text-to-speech and speech-to-text routes |
| Web Search | Current-public-information search backend |
Inspect a tool
Select a built-in or MCP tool to review:
- source and toolset;
- description and input schema;
- timeout; and
- visible and stored output budgets.
The input schema is the contract Anyy uses when calling the tool. MCP tool definitions come from the live server catalog; manage which remote tools are exposed on MCP.
Runtime information
The detail page displays the current timeout and visible/stored output budgets. Tool descriptions, schemas and resource settings are read-only on this page. Definitions come from the tool implementation or MCP server catalog. Configure visibility through the capability backend, MCP selection and Toolsets.
Codemode settings
Open Tools → Built-in → codemode. Codemode lets the model call the Session's available tools through JavaScript. Its settings have two separate scopes.
Profile defaults
Choose an activation setting and a shared call mode, then Save:
| Activation | Effect |
|---|---|
| Use current tool selection | Follow the existing selection and MCP auto-activation rules; this does not mean disabled |
| Enable | Add Codemode to new Session defaults without enabling other tools |
| Disable | Explicitly exclude Codemode from new Session defaults |
| Mode | When Codemode is active |
|---|---|
| Direct calls and scripts (on) | Keep direct tool entries alongside scripts |
| Concentrate calls in scripts (only) | Hide script-callable direct entries; those tools remain available through Codemode |
The mode is shared by the Profile and applies at the next preparation. It does not change an already prepared request. Saving the activation default does not reselect tools in existing Sessions. The page reports Applied or Saved, not yet applied; after an external configuration edit, explicitly save here or restart the Gateway. Provider reload does not apply tool settings.
Other tool rules and broader exclusions remain in place. If changing Codemode alone would also change other tool rules, the save is rejected and the original configuration is preserved. This page does not turn Codemode into a Role or edit general tool definitions.
An existing Session
- Choose a Session in Session override and inspect its state.
- Select Enable or Disable while it is idle with no pending input.
- Choose Apply to Session and check the returned state.
This changes only Codemode while preserving the Session's other active tools and selection rules. It cannot expand that Session's allowed tool list, so a Profile default may be enabled while an older restricted Session still cannot enable it. Busy Sessions must become idle first. Not loaded yet means its resident tool state has not been observed, rather than a confirmed disabled state. There is no separate Session mode. Profile Save and Session Apply are independent actions.
MCP and tool search
MCP can automatically activate Codemode when its configuration allows it. Use current tool selection preserves that behavior. Explicit exclusions still apply. Tool search is independent: disabling Codemode does not disable MCP or tool search, and an active allowed tool search can still discover indirect MCP tools. The page shows that remaining route when available.
For CLI selection and manual configuration, see Toolsets. See Codemode for script APIs and Tool Search for discovery and next-request activation.
Configure capability backends
The capability cards guide setup and health checks:
- Web Search selects a provider, endpoint, and credential, then verifies it.
- Image, Video, and Voice reuse the model configuration surface for their dedicated routes.
CLI equivalents
List configured capabilities:
anyy tools list
Run interactive setup or probe a capability:
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
Tool visibility
A configured backend is not necessarily visible in an existing session. Toolsets are resolved against the selected Profile and session context. After enabling a new capability, verify its backend and Session selection. For Codemode, use the explicit Session action above; changing a Profile default alone leaves an existing Session unchanged.
Troubleshooting
| Problem | Fix |
|---|---|
| Tool is listed but absent from a session | Check its capability backend and toolset configuration |
| MCP tool is missing | Check server enablement/exposure and Session selection; probe or reload the server when needed |
| Tool output is cut off | Follow its continuation hint, use tool_result_read for an inspectable result ref, or request a narrower result |