Achilles — Admin: AI tools

The tools the platform gives models as a tool schema. Each tool lives on two surfaces, and each is enabled separately: chat and agents. Concept and roles — Tool catalog. Out of the box, both presets are off.

Tool catalog → Data model → Tool-calling harness

Two read-only platform presets. Off by default: external egress is opened deliberately.

tools · registry

achilles.local/admin/ai-tools /admin/ai-tools · Owner / Admin

AI tools Two independent switches on each tool — In chat (the model sees it in conversation) and For agents (an owner can assign it to an agent). A gray pill means off; a click turns it on.

Web search web_search Tavily · key set checked · 2 min ago Configure 1

In chat For agents

Fetch URL fetch_url no key needed not checked Check

In chat For agents

Knowledge Store · core search · graph · sql core · read-only · always on, no configuration needed 2

External MCP servers v2 connecting servers and write tools — next iteration

The list is a live registry of types. An organization’s own tool, registered as a class in code, appears here on its own after a restart — as a row, like the presets, and off. Enabling a tool and changing a setting (provider, key) are written to the audit log as an admin action. A call limit / budget for web_search is v2.

web search · “Configure”

Configure

Provider Tavily ▾ Tavily · Brave · Serper · Google CSE — the model sees one tool

API key

••••f3a1

entered once — never shown again

provider responded

a ping to the provider, not a real model request; the result lands in status · last_check_at

1 Configure gathers all of a tool’s settings into one popover: provider (Tavily · Brave · Serper · CSE), API key (a “set” flag, not the secret — it’s encrypted by the Auth crypto core and never returned) and a Test button — a ping to the provider, with the result in status · last_check_at, shown on the card as a pill. fetch_url has nothing to configure — only “Check” (egress availability). Same approach as the AI model provider check.
2 The KS core is a reference row: the three tools are always available to chat and agents, with no separate configuration. Removing an added tool is graceful degradation — the agent carries on with the core.
3 Connecting external MCP servers and write tools is v2; the button is disabled.