Skip to main content
Glama
Sign In
react-render-profile-mcp

react-render-profile-mcp

by vola-trebla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remediate_component

Optimizes React components by hoisting static code, memoizing unstable props with useCallback/useMemo, and applying React.memo when ROI exceeds 1.5. Edits the component file directly.

Instructions

Automatically optimizes a React component's AST by hoisting static declarations, wrapping unstable callbacks/objects in useCallback/useMemo, and wrapping the component in React.memo if the ROI score is above 1.5. Mutates the file on disk.

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": {
      "file_path": "<file_path>",
      "component_name": "<component_name>",
      "unstable_props": "<unstable_props>",
      "roi_score": "<roi_score>"
    },
    "name": "remediate_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the React component file on disk
roi_scoreYesEstimated ROI score from profiling (usually 0 to 5) justifying memoization overhead
component_nameYesName of the React component to optimize
unstable_propsYesComma-separated or space-separated list of props to memoize/wrap in hooks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states 'Mutates the file on disk' and lists the AST transformations performed. It could add details about irreversibility or file backup, but the core mutation behavior is clearly disclosed.

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?

Two sentences cover action, target, specific transformations, threshold condition, and mutation warning. No redundant phrasing; every clause earns its place. Front-loaded with 'Automatically optimizes' for quick comprehension.

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 no output schema and a clear action-oriented role, the description is complete for a mutation tool. It covers behavior, mutation, and input semantics via the schema and description. Minor gaps include error handling and rollback details, but these are not critical given the schema and sibling context.

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%, so the baseline is 3. The description adds value by explaining the ROI threshold (1.5) that triggers React.memo and clarifies that unstable_props are wrapped in hooks, providing context beyond the individual property descriptions.

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 that the tool automatically optimizes a React component's AST with specific transformations (hoisting, useCallback/useMemo, React.memo). This distinguishes it from all sibling analysis tools, which focus on profiling and diagnosis rather than modification.

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

Usage Guidelines3/5

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

The description gives a condition for using the tool (ROI score above 1.5) but does not explicitly state when to use it instead of sibling tools like suggest_memoization or diagnose_hydration_and_suspense. It implies usage after profiling, but lacks explicit exclusions or alternative 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