React Native Expo MCP

Overview Schema Source Related Servers Discussions Admin

optimize_performance

Analyze React Native app performance and get targeted optimization tips for common scenarios like list rendering, navigation, animations, memory, bundle size, or startup time on iOS or Android.

Instructions

Get performance optimization suggestions for React Native

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": {
      "scenario": "<scenario>"
    },
    "name": "optimize_performance"
  }
}

Input Schema

Name	Required	Description	Default
`scenario`	Yes	Performance scenario to optimize
`platform`	No	Target platform

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 29, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it returns suggestions, but does not indicate whether it is read-only, requires network access, or what the generation method is. Lacks important behavioral context 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 could include more useful information without becoming verbose. It is adequately structured but minimal.

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 no description of return format or behavior. Given the tool has multiple enum scenarios, the description is insufficient for an agent to understand expected output or side effects. More context is needed for complete understanding.

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?

Input schema has 100% description coverage for both parameters, with clear enum options. The description adds no extra meaning beyond the schema; baseline is acceptable at 3 since schema already documents parameters well.

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?

Description clearly states it provides performance optimization suggestions for React Native. It uses verb 'Get' and resource 'performance optimization suggestions', and the platform is specified. However, it doesn't fully distinguish from sibling tool 'analyze_codebase_performance' which may have overlap.

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. Does not mention prerequisites, limitations, or when not to use it. The description only states what it does, leaving the agent without context for choosing among similar tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.