Skip to main content
Glama
Sign In
https://github.com/Streen9/react-mcp

https://github.com/Streen9/react-mcp

by kalivaraprasad-gonapa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run-command

Execute terminal commands to build and modify React apps based on user prompts. Specify a directory for command execution.

Instructions

Run a terminal command

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
commandYesCommand to execute
directoryNoDirectory to run the command in (defaults to current directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects, permissions, error behavior, or what happens to the terminal session. The minimal description fails to add necessary transparency beyond the bare purpose.

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?

Single sentence, no wasted words. However, it could be slightly more informative without becoming verbose, so not a perfect 5.

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?

For a command-runner with security implications and no output schema, the description lacks completeness. No mention of return values, error handling, or prerequisites relative to siblings. Schema richness is low, so description should compensate but does not.

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% with both parameters having descriptions ('Command to execute' and 'Directory to run the command in'). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Run a terminal command', which is clear in verb and resource but lacks specificity about the type of command (e.g., shell command). It does not differentiate from siblings like 'get-process-output' or 'install-package', which also involve running commands.

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 on when to use this tool versus siblings (e.g., run-react-app for starting an app, install-package for package installation). The description provides no context for selection.

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