Skip to main content
Glama

run_task

Execute a discovered task in a subprocess, stream stdout and stderr as notifications, and return exit code plus output; supports stdin input and project selection.

Instructions

Execute a discovered task in a subprocess. Streams stdout as info and stderr as warning notifications; returns exit_code, stdout and stderr. Supply stdin for interactive input. Select project when multiple projects are registered.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_name": "<task_name>"
    },
    "name": "run_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
stdinNo
projectNoRegistered project alias or path.
timeoutNo
task_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral burden. It usefully discloses subprocess execution, that stdout/stderr are streamed as info/warning notifications, and that exit_code, stdout and stderr are returned. It says nothing about side effects or safety of running arbitrary task code, permission requirements, timeout behavior, or what happens on non-zero exit or failure.

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?

Four short sentences, front-loaded with the action and execution model before the return behavior and parameter hints. Nothing is redundant, though the sentences are telegraphic and could group the return/streaming details more clearly.

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

Completeness3/5

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

For a five-parameter execution tool with no annotations and no output schema, the description does cover the return shape and streaming channels, which is the most important missing structured data. However, it omits timeout/termination semantics, failure behavior, and args semantics, so it is adequate but incomplete.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description should compensate for the undocumented parameters. It explains stdin's purpose and the project selection condition, but args, timeout (default 60) and the task_name format remain undocumented in both schema and description, leaving three of five parameters semantically bare.

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?

"Execute a discovered task in a subprocess" gives a specific verb and resource plus the execution mechanism, which separates it from the sibling list_tasks (listing vs running). It stops short of naming list_tasks as the source of "discovered" tasks, so the pairing is implied rather than stated.

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

Usage Guidelines3/5

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

Two conditional cues are given: "Supply stdin for interactive input" and "Select project when multiple projects are registered," which tells the agent when each optional parameter matters. There is no guidance on when to prefer this tool over list_tasks, no prerequisites, and no exclusions, so usage is implied rather than fully framed.

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

Deploy Server

Other Tools