Skip to main content
Glama
Sign In
React Native Expo MCP

React Native Expo MCP

by Divagnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_component

Analyzes React Native components to enforce best practices, improve code quality, and identify issues in functional, class, or hook components.

Instructions

Analyze React Native component for best practices

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoReact Native component code to analyze. If not provided, analyzes entire codebase
typeNoComponent type
codebase_pathNoPath to React Native project root for codebase analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It does not disclose what the analysis entails (e.g., what specific best practices are checked), any side effects, or output format. The minimal description fails to inform the agent about the tool's behavior.

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 a single sentence that clearly states the verb and resource, but it is too brief and omits important context. While concise, it sacrifices informational value.

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 the tool has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the relationship between parameters (e.g., code vs. codebase_path) or the nature of the analysis results, leaving the agent with significant uncertainty.

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 descriptive parameter explanations (e.g., code: 'If not provided, analyzes entire codebase'). The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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's action ('Analyze') and target ('React Native component for best practices'). It is specific enough to understand the basic purpose, but it does not distinguish from sibling tools like analyze_codebase_comprehensive or optimize_performance.

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 is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusions mentioned. The description does not help an agent decide between this and similar analysis tools.

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