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

create-react-app

Initialize a React project with a specified name, optional template, and base directory.

Instructions

Create a new React application

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": {
      "name": "<name>"
    },
    "name": "create-react-app"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the React app
templateNoTemplate to use (e.g., typescript, cra-template-pwa)
directoryNoBase directory to create the app in (defaults to home directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations provided, and the description only says 'Create a new React application' without disclosing behavioral traits (e.g., file creation, dependency installation, destructiveness). This is insufficient for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise, but it lacks additional structure or context. It is not overly verbose, but could include more essential info without harming 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?

No output schema, and description does not explain return values or side effects. For a tool that creates files and runs commands, this is incomplete.

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 coverage is 100%, so baseline applies. The description adds no meaning beyond the schema, which already describes the parameters. Adequate but not enhanced.

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 tool creates a new React app, which is a specific verb+resource. However, it does not differentiate from sibling tools like run-react-app, but the purpose is clear.

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 alternatives like run-react-app or install-package. The description lacks 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