Agent tools & MCP
This page describes the tool surfaces Runink TIDE’s agents use.
1. The coding-session tools
tide session does not use MCP. Its tools are a fixed set, requested by the model as TOON (with a JSON fallback). There is no native function calling on this inference plane:
| Tool | Gate |
|---|---|
read_file, list_dir, write_file, git_diff | confined to the workspace; .git and symlink escapes refused |
run_shell | human y/N on every call, plus a denylist (unless a --verify tier admits the command) |
file_issue | human y/N |
browser_navigate, browser_click, browser_type, browser_read, browser_screenshot, browser_console | only with --browser; human y/N; localhost unless --browser-allow-remote |
done | ends the run |
Details: Coding Sessions.
2. The console’s Ask tools
The console serves a grounded question API, AskService. Its tools are read-only, in-process calls of methods the console already serves, and no Ask tool dials a tenant source. AskService.Describe lists, per scope, the tools the model may call. See Ask.
3. The MCP server library, mesh/mcp (FACE)
mesh/mcp is an in-house MCP server: JSON-RPC 2.0 over Server-Sent Events. Its diagnostics server registers these tools:
| Tools |
|---|
check_health, get_metrics_summary, system_info, actor_list, evaluate_policy, ebpf_telemetry |
analyze_telemetry |
InspectNodeState |
The mesh, MCP and object-store features are FACE-only; PULSE shares only inference and mesh/selfheal. tide dev up starts the app backends with “diagnostics/MCP” enabled locally.