Skip to main content
Glama

ng_run

Execute custom Angular CLI architect targets like app:build:production to automate build, test, and deployment workflows directly from your development environment.

Instructions

Run 'ng run' to execute a custom architect target

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesThe target to run (e.g., app:build:production)
appRootYesThe absolute path to the first folder in the 'path' property. For example, if 'path' is 'webui/src/app/modules/alerts', then 'appRoot' should be the absolute path to 'webui'.
optionsNoAdditional options for ng run

Implementation Reference

  • The switch case in handleToolCall that sets up the command for 'ng_run': runs 'npx ng run <target>' with options from the cwd set to appRoot.
    case "ng_run": {
      command = "npx";
      commandArgs = ["ng", "run", args.target];
      if (args.options) {
        for (const [key, value] of Object.entries(args.options)) {
          commandArgs.push(`--${key}`, String(value));
        }
      }
      break;
    }
  • The tool definition object for 'ng_run' including name, description, and input schema validation.
    {
      name: "ng_run",
      description: "Run 'ng run' to execute a custom architect target",
      inputSchema: {
        type: "object",
        properties: {
          target: {
            type: "string",
            description: "The target to run (e.g., app:build:production)",
          },
          appRoot: {
            type: "string",
            description:
              "The absolute path to the first folder in the 'path' property. For example, if 'path' is 'webui/src/app/modules/alerts', then 'appRoot' should be the absolute path to 'webui'.",
          },
          options: {
            type: "object",
            description: "Additional options for ng run",
            additionalProperties: { type: "string" },
          },
        },
        required: ["target", "appRoot"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions execution but doesn't clarify if this is a read-only or destructive operation, what permissions are needed, or any side effects like file modifications. This is inadequate for a tool that likely performs builds or similar actions.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded and appropriately sized for its purpose, earning full marks for conciseness.

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

Completeness2/5

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

Given the complexity of executing custom architect targets (likely involving builds or deployments), no annotations, and no output schema, the description is insufficient. It doesn't explain what happens during execution, potential outputs, or error handling, leaving significant gaps for the agent.

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 schema already documents all parameters thoroughly. The description adds no additional meaning beyond implying 'ng run' execution, which is redundant with the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Run') and resource ('custom architect target'), making the purpose understandable. However, it doesn't differentiate from sibling tools like ng_generate or ng_update, which also execute Angular CLI commands, so it doesn't reach the highest clarity level.

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 is provided on when to use this tool versus alternatives like ng_generate or ng_add. The description merely states what it does without context about appropriate scenarios or prerequisites, leaving the agent to infer usage.

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/talzach/mcp-angular-cli'

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