Skip to main content
Glama

project_task_run

Run predefined npm build, test, lint, typecheck, or check tasks in an approved local project and return the exit code and logs for reviewing results.

Instructions

Run a predefined npm build/test/lint task in an approved local project and return the exit code and logs. Requires BRIDGE_PROJECT_COMMANDS_ENABLED=1.

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": {
      "project_path": "<project_path>",
      "task": "<task>"
    },
    "name": "project_task_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the output contract (exit code plus logs) and an environment-flag requirement, both of which the structured fields do not carry. It does not explain whether a non-zero exit surfaces as an error or a normal result, nor what 'approved' means operationally, which keeps this from a 5.

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 sentences, no filler, with the operation stated first and the prerequisite second. Every clause earns its place.

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 two-parameter tool with no output schema, the description covers the operation, the return shape, and the enabling flag. It is still thin on failure semantics (non-zero exit handling) and on what qualifies a project for execution, both of which matter before invoking a task runner.

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 0%, so the description must carry parameter meaning and largely does not. The task enum is self-explanatory in the schema, but project_path is never clarified (absolute vs relative, how a project becomes 'approved'), leaving the required path parameter underspecified.

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?

The description gives a specific verb and resource ('Run a predefined npm build/test/lint task in an approved local project') plus the return payload ('exit code and logs'). It implicitly separates itself from terminal_run by stressing 'predefined' tasks, but never names or contrasts a sibling explicitly.

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?

The gating prerequisite (BRIDGE_PROJECT_COMMANDS_ENABLED=1) and the 'approved local project' constraint are stated, which tells the agent when the call can succeed. There is no guidance on choosing this over terminal_run for ad-hoc commands or over project_task_plan, leaving the alternative-selection decision to inference.

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