Skip to main content
Glama
Sign In
React Development Workflow MCP Server

React Development Workflow MCP Server

by rushit-simform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

commit_and_push

Commit project changes to a specified Git branch and push to GitHub, with optional file selection.

Instructions

Commit changes and push to GitHub branch

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": {
      "message": "<message>",
      "branch": "<branch>"
    },
    "name": "commit_and_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoFiles to commit (if empty, commits all)
branchYesBranch to push to
messageYesCommit message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It doesn't disclose side effects like modifying the remote repository, requiring authentication, or behavior when files list is empty (despite schema noting it). It is a minimal action statement without broader behavioral context.

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?

One clean, front-loaded sentence with no wasted words. However, it is extremely terse and could benefit from a bit more context, 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?

This is a mutation without annotations or output schema. The description doesn't cover usage, prerequisites, or potential side effects. While schema covers parameters, the description is too thin for an operation that modifies repository state.

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 each parameter is already documented. The description adds no additional parameter semantics beyond what the schema provides, earning the baseline score.

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 a specific verb ('Commit') and resource ('changes', 'GitHub branch'), accurately distinguishing this from sibling tools like create_pull_request or create_feature_branch.

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 vs alternatives. It lacks any context about development workflow or exclusions, such as when to use create_feature_branch or create_pull_request.

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