React Native Expo MCP

by Divagnz

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

expo_upgrade

Upgrade Expo SDK and dependencies to a specified newer version, with dry-run preview and npm/yarn option.

Instructions

Upgrade Expo SDK and dependencies to newer version

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": "expo_upgrade"
  }
}

Input Schema

Name	Required	Description
`target_version`	No	Target Expo SDK version (or latest)
`dry_run`	No	Preview changes without applying
`npm`	No	Use npm instead of yarn

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral traits like side effects (e.g., file modifications), network requirements, or handling of breaking changes. The description alone is insufficient for a mutation tool.

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?

Single, front-loaded sentence with no fluff. Every word contributes to the purpose.

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 is too minimal for a complex SDK upgrade operation. Missing details on return values, error handling, and sequence effects.

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 the schema already documents all parameters. The description adds no extra meaning beyond the schema, thus baseline of 3 is appropriate.

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 the verb 'upgrade' and the resource 'Expo SDK and dependencies', effectively distinguishing it from siblings like 'upgrade_packages' which focuses on general package upgrades.

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 such as 'check_for_updates' or 'migrate_packages'. Lacks context on prerequisites or when not to use.

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