Skip to main content
Glama
Sign In
React Native MCP Server

React Native MCP Server

by MrNitro360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

refactor_component

Refactor React Native component code to improve performance, maintainability, accessibility, type safety, or modern patterns. Specify target RN version and optionally include test updates.

Instructions

Provide expert-level refactoring suggestions and implementations

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": {
      "code": "<code>",
      "refactor_type": "<refactor_type>"
    },
    "name": "refactor_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesReact Native component code to refactor
refactor_typeYesType of refactoring to apply
target_rn_versionNoTarget React Native version for refactoring
include_testsNoWhether to include test updates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'suggestions and implementations'. It does not clarify whether the tool modifies code, returns modified code, or provides suggestions. Behavioral traits like mutability, permissions, or side effects are absent, leaving significant ambiguity for a refactoring action.

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?

The description is extremely concise (one sentence), which avoids verbosity but lacks key information. It does not front-load the most critical details (e.g., that it operates on React Native components) and is too brief to be helpful beyond stating the obvious.

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 no output schema and no annotations, the description fails to explain what the tool returns (suggestions vs. code changes) or how to interpret results. The 4 parameters and lack of output details leave the agent with incomplete context for correct invocation.

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% with descriptions for all 4 parameters. The description adds no additional meaning beyond the schema, which already explains each parameter. Baseline score of 3 is appropriate since the description does not enhance understanding of the parameters.

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 'Provide expert-level refactoring suggestions and implementations' clearly states that the tool performs refactoring on React Native components. It differentiates from siblings like 'analyze_component' (analysis) and 'remediate_code' (fixing) by focusing on refactoring. However, it remains somewhat generic and could explicitly reference component refactoring.

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?

The description provides no guidance on when to use this tool versus sibling tools. No mention of prerequisites, context, or alternatives (e.g., 'Use analyze_component first to identify issues'). The agent receives no help in deciding between this and related tools like 'remediate_code' or 'optimize_performance'.

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