Skip to main content
Glama
Sign In
Project Navigator MCP Server

Project Navigator MCP Server

by hrustalevdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

run_command

Run pre-approved shell commands to build, test, lint, or type-check code, enabling automated quality checks.

Instructions

Run a whitelisted shell command. Allowed commands: npm run build, npm test, npm run lint, npm run dev, npx tsc --noEmit

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": {
      "command": "<command>"
    },
    "name": "run_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesExact command string (must match whitelist exactly)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It states the tool runs whitelisted shell commands but does not disclose output handling, error behavior, or whether the command runs in a specific directory or environment. This is adequate but not detailed.

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 sentence of 15 words, extremely concise with no fluff. It front-loads the purpose and immediately lists allowed commands.

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 a simple tool with one parameter and no output schema, the description covers the essential constraint (whitelist). It could be improved by mentioning that output is returned as stdout/stderr or that errors are non-zero exit codes, but it is largely sufficient for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds value by listing allowed command strings beyond the schema's generic description. The schema says 'must match whitelist exactly', and the description makes the whitelist explicit.

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 verb 'Run' and the resource 'whitelisted shell command', listing specific allowed commands. It clearly distinguishes from sibling tools like find_files and search_code which are not shell execution.

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

Usage Guidelines4/5

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

The description explicitly lists allowed commands (npm run build, npm test, etc.), indicating when to use the tool. It does not explicitly state when not to use it or provide alternatives, but the whitelist serves as clear guidance.

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