Skip to main content
Glama

nexus_agent_run

Run an autonomous agent that reads files, writes code, executes commands, and searches the web, iterating until the task is done, returning the final answer and full action trace.

Instructions

Run an autonomous AI agent that can read files, write code, execute shell commands, search the web, and iterate until the task is complete. The agent uses the specified model (GPT-5.4, Nemotron, Gemini, etc.) and works independently through a ReAct loop. Returns the final answer plus a full trace of every action taken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoOptional label for this agent (e.g., "coder", "reviewer")
taskYesWhat the agent should accomplish. Be specific.
modelYesModel ID to use (e.g., "gpt-5.4", "nvidia/nemotron-3-super-120b-a12b")
providerYesProvider ID (e.g., "openai", "nvidia", "gemini", "groq")
maxTimeMsNoTotal timeout in milliseconds (default: 300000 = 5 minutes)
maxTokensNoMax tokens per model call
workingDirNoDirectory the agent can read/write files in (default: current project directory)
temperatureNoSampling temperature (0.0-2.0)
enabledToolsNoTools to enable. Available: read_file, write_file, edit_file, list_directory, search_files, run_command, web_fetch, think. Default: all tools.
systemPromptNoCustom agent persona or additional instructions
maxIterationsNoMax agent loop iterations (default: 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the ReAct loop, autonomy, tool access, and the two-part return (final answer + full trace), which is meaningful transparency for an agent runner. It does not mention side-effect risk or auth requirements, but what it states is clear and non-contradictory.

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

Conciseness5/5

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

Two compact sentences; the first sentence front-loads the core action and capabilities, and the second explains the execution model and return value. Nothing is wasted.

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 high parameter count, no output schema, and no annotations, the description supplies the essential behavior and return shape while the schema covers parameter details. It could note timeouts or side effects, but overall it is sufficient for an agent to invoke the tool correctly.

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 the baseline 3 applies. The description adds examples of model IDs and providers and maps capabilities to tool names, but it does not significantly alter or deepen parameter meaning beyond the schema.

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

Purpose4/5

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

States a specific verb and resource: 'Run an autonomous AI agent' with a concrete list of capabilities and a ReAct-loop execution model. This clearly identifies the tool as a single-agent orchestration run, though it does not explicitly contrast with subagent/multi-agent siblings.

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

Usage Guidelines2/5

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

No guidance about when to choose this over nexus_subagent_run, nexus_subagent_spawn, or nexus_agent_multi. The capability list implies use for end-to-end autonomous tasks, but there are no exclusions or alternative routing conditions.

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