Skip to main content
Glama

oz_agent_run

Run a local Warp Oz AI agent for coding tasks like refactoring, testing, debugging, or explaining code. Agent can create or modify files in the workspace and uses no cloud credits.

Instructions

Run a Warp Oz AI agent locally in the host workspace and return its full output synchronously. Runs oz agent run with your prompt and blocks until the agent finishes. Use for local coding tasks — refactor, write/run tests, debug, explain code — that should NOT consume cloud credits; for cloud execution call oz_agent_run_cloud instead. NOT read-only: the agent may create or modify files in the workspace. Requires the oz CLI on PATH (install Warp).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoAI model id to use, from `oz_list_models` (e.g. `claude-4-8-opus-max`). Omit to use the configured default (`auto` lets Warp choose).
skillNoAgent skill id from the 7-stage pipeline (e.g. `5-test-agent`). Omit to let the CLI choose one based on the prompt.
promptYesNatural-language instruction for the agent, e.g. "add unit tests for src/auth.ts".
profileNoOz agent profile name (managed in the Warp app under Settings → AI → Profiles). Omit to use the default profile.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It clearly states the tool is synchronous, local, and not read-only (may create or modify files). It does not mention rate limits or detailed auth, but the key behavioral traits are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core purpose, followed by usage, behavioral note, and prerequisite. It is concise and each sentence adds value, though it could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity and lack of output schema, the description covers the main aspects: local execution, synchronous blocking, file modification, and prerequisites. It is fairly complete for an agent-run tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds slight value by clarifying default behavior for model and skill, but does not significantly enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs a Warp Oz AI agent locally, using 'oz agent run', and distinguishes it from cloud execution by naming the sibling `oz_agent_run_cloud`. The verb 'run' and resource 'agent' are explicit, and the purpose is well-defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use the tool (local coding tasks, not consuming cloud credits) and when not to (cloud execution, pointing to `oz_agent_run_cloud`). It also lists example tasks and mentions the prerequisite of having the `oz` CLI on PATH.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sena-labs/OzBridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server