ToolConventions

The agent-server tool conventions this library follows (Pydantic AI Harness, AGENTS.md §1.4) translated into the model, for tool calls that arrive over a protocol (AI SDK, AG-UI) rather than from an on-device dev.ai.elements.core.agent.AgentTool, which declares them itself:

  • delegate_task(agent_name, task) → ToolKind.Delegation

  • load_capability(id) → ToolKind.Skill

  • the Harness FileSystem and Shell tools → a ToolCategory and location, exactly as the Harness ACP adapter presents them (pydantic_ai_harness.experimental.acp default_coding_presenter): read_file / file_info read, edit_file / write_file edit, list_directory / search_files / find_files search, run_command / start_command / check_command / stop_command execute, create_directory other; path is the location.

This is the only place those names are interpreted; UI elements look at the model alone.

Functions

Link copied to clipboard
fun categoryOf(name: String, arguments: JsonObject?): ToolCategory?

The ToolCategory of a Harness file-system or shell call, or null for any other tool.

Link copied to clipboard
fun kindOf(name: String, input: String): ToolKind?
Link copied to clipboard
fun locationOf(name: String, arguments: JsonObject?): String?

The path a Harness file-system call acts on (its ACP ToolCallLocation), or null.