ArchAstro. V1. Agents. AgentTools
(archastro v0.2.0)
Copy Markdown
AgentAgentTool API resource.
Summary
Functions
Create an agent tool
Functions
@spec create( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.PostApiV1AgentsAgentAgentTools.Input.t() ) :: {:ok, ArchAstro.Types.AgentTool.t()} | {:error, ArchAstro.Error.reason()}
Create an agent tool
Creates a new tool and attaches it to the specified agent. Tools can be
either "builtin" (a platform-provided capability identified by
builtin_tool_key) or "custom" (a caller-defined tool with its own name,
description, parameter schema, and handler).
New tools are created in "draft" status by default unless status: "active" is explicitly supplied. Draft tools are not exposed to the LLM
during agent runs; call the activate endpoint to promote them.
For built-in tools that support multiple instances per agent (those whose
catalog entry has a multi_instance_mode), supply name_prefix to
namespace the LLM-facing tool names. Requires app scope.
The newly created tool.
@spec list( ArchAstro.Client.t(), String.t(), ArchAstro.Types.Operations.GetApiV1AgentsAgentAgentTools.Params.t() ) :: {:ok, ArchAstro.Types.AgentToolListResponse.t()} | {:error, ArchAstro.Error.reason()}
List agent tools
Returns all tools for the authenticated app, optionally filtered by agent or tool kind. Both explicitly created tools and tools derived from connected integrations (installation-sourced tools) are included in the response.
Installation-sourced tools appear with source: "installation" and
status: "active". They are synthesized at request time from connected
integrations and do not have a persistent tool ID of the atl_... form;
their id is a composite of the installation ID and server tool type.
Use the agent filter to retrieve tools for a specific agent. Supplying an
agent ID that does not belong to the authenticated app returns 404.
Requires app scope.
List of tools matching the supplied filters.