Skip to main content
Glama
patrickkabwe

React Native Upgrader MCP

by patrickkabwe

Get Stable Version

get-stable-version

Retrieve the current production-ready React Native version for upgrade planning. Provides the stable release number to use with migration tools.

Instructions

Gets the latest stable version of React Native from GitHub releases.

OVERVIEW: This version represents the most recent production-ready release that has been thoroughly tested and is recommended for use in applications.

VERSION FORMAT: • The version number follows semantic versioning (e.g. 0.72.0) • Excludes any release candidates or beta versions

USAGE: • This tool is commonly used before planning an upgrade to ensure targeting the latest stable release • Must be called before calling get-react-native-diff tool • The output of this tool will be used as the toVersion parameter in the get-react-native-diff tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function that calls getStableVersion helper and formats the response as MCP tool output.
    async () => {
        const version = await getStableVersion();
        return {
            content: [{ type: "text", text: version }]
        }
    }
  • src/tools.ts:36-60 (registration)
    Registration of the 'get-stable-version' tool including title, description, and handler function.
        server.registerTool('get-stable-version',
            {
                title: "Get Stable Version",
                description: `Gets the latest stable version of React Native from GitHub releases.
    
    OVERVIEW:
    This version represents the most recent production-ready release that has been thoroughly tested 
    and is recommended for use in applications.
    
    VERSION FORMAT:
    • The version number follows semantic versioning (e.g. 0.72.0)
    • Excludes any release candidates or beta versions
    
    USAGE:
    • This tool is commonly used before planning an upgrade to ensure targeting the latest stable release
    • Must be called before calling get-react-native-diff tool
    • The output of this tool will be used as the toVersion parameter in the get-react-native-diff tool`,
            },
            async () => {
                const version = await getStableVersion();
                return {
                    content: [{ type: "text", text: version }]
                }
            }
        );
  • Core helper function implementing the logic to fetch the latest stable React Native version from GitHub API by getting the latest release tag and stripping the 'v' prefix.
    export const getStableVersion = async () => {
        const response = await fetch(`https://api.github.com/repos/facebook/react-native/releases/latest`);
        const data = await response.json() as { tag_name: string };
        return data.tag_name.replace('v', '');
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the version is 'production-ready' and 'thoroughly tested,' which adds context about reliability. However, it doesn't mention potential rate limits, authentication needs, or error behaviors, leaving some gaps in behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections (OVERVIEW, VERSION FORMAT, USAGE) and uses bullet points for clarity. It's appropriately sized, but some sentences could be more concise (e.g., 'This version represents...' is slightly verbose). Overall, it's efficient and front-loaded with key information.

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 the tool's low complexity (0 parameters, no output schema), the description is mostly complete. It explains the purpose, usage guidelines, and output format. However, it lacks details on error handling or what happens if no stable version exists, which could be relevant for an AI agent.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on usage and output context without redundant parameter info, earning a baseline score of 4 for this scenario.

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 tool's purpose: 'Gets the latest stable version of React Native from GitHub releases.' It specifies the exact resource (React Native), source (GitHub releases), and distinguishes it from siblings like get-rc-version (which would get release candidates) and get-user-version (which appears to get user-specific versions).

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: 'before planning an upgrade to ensure targeting the latest stable release' and 'Must be called before calling get-react-native-diff tool.' It also distinguishes it from alternatives by noting it excludes 'release candidates or beta versions,' which implies get-rc-version is for those cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/patrickkabwe/react-native-upgrader-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server