Skip to main content
Glama

run_async

Destructive

Execute a project's planned tasks in the background, returning a run ID immediately. Use when tasks are already planned and you need non-blocking execution.

Instructions

Start executing a project's planned tasks in the BACKGROUND.

Use when: a devplan exists and you want it executed without blocking — like
``run`` but returns a ``run_id`` immediately. Poll ``job_status``, cancel
with ``stop_job``. Do NOT use to plan from a goal — that is ``build_async``.
Related: ``run`` (synchronous), ``build_async``.

DESTRUCTIVE side effects (once running): edits files, makes git commits, and
calls an external LLM provider. Refuses a second job for a project that
already has one running.

Returns ``{run_id, status}``, or ``{error}`` when one is already running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a project with planned tasks (a devplan). Example: '/Users/me/code/my-api'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes destructive side effects (edits files, git commits, calls LLM) and refusal of second job, adding context beyond the annotations which already set destructiveHint=true.

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?

The description is very concise, with the purpose stated first, followed by usage guidelines and behavioral details, all in a few sentences without waste.

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

Completeness5/5

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

Given the complexity of an async job with destructive effects, the description covers return values, error case (job already running), and side effects. The output schema is referenced but not detailed, which is acceptable.

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?

The input schema already provides a detailed description of the 'path' parameter, including examples and requirements. The tool description adds little extra meaning, so it meets the baseline for high schema coverage.

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 starts executing planned tasks in the background, using the verb 'Start' and resource 'project's planned tasks'. It also distinguishes from siblings like 'run' (synchronous) and 'build_async'.

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?

Explicitly says when to use (devplan exists, want async) and when not to (planning from a goal, use build_async). Lists alternatives: 'run' (synchronous) and 'build_async'.

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/dcondrey/misterdev'

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