Summary
Seven tool definitions regardless of how many agents you have is the point of this design.
If every agent were a tool, an organisation with fifty would pay for fifty definitions in every request. Routing through a call tool keeps the standing cost fixed and puts discovery behind an explicit list call. The authoring tools being present only on servers configured for it is the other sensible split — a client that runs agents does not need one that can create them.
What it is
Logic's endpoint. The design decision is that agents are not exposed as tools — the client sees seven built-ins, and any agent is invoked through the call tool by name.
What you get
- _logic_list_agents and _logic_read_agent — discover what exists and what it does
- _logic_call_agent — invoke one, and _logic_check_execution_status to follow it
- _logic_view_executions — the history
- _logic_create_agent and _logic_patch_agent — authoring, available only on servers with authoring enabled
Requirements
A bearer token, on a per-server URL.
Setup effort
Paste a URL with a key — add the endpoint to your client