Skip to main content
Glama
patrickkabwe

React Native MCP Server

by patrickkabwe

Get Stable Version

get-react-native-stable-version

Retrieve the current stable React Native version for planning upgrades and ensuring compatibility with production applications.

Instructions

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

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

The version number follows semantic versioning (e.g. 0.72.0) and excludes any release candidates or beta versions.

This tool is commonly used before planning an upgrade to ensure targeting the latest stable release and 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

  • src/tools.ts:36-60 (registration)
    Registers the 'get-stable-version' tool, which retrieves the latest stable React Native version from GitHub. Note: This appears to be the tool matching the query intent, as no exact 'get-react-native-stable-version' was found.
        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 handler function that executes the tool logic by fetching the latest stable React Native version from GitHub releases API.
    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', '');
    }
  • Imports the getStableVersion helper function used by the tool handler.
    import { getCurrentReleaseCandidateVersion, getDiff, getStableVersion } from "./services";
  • src/server.ts:17-17 (registration)
    Calls registerTools which includes registration of the get-stable-version tool.
    registerTools(server);
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool fetches from GitHub releases, returns semantic versioning format, excludes unstable versions, and that the output is production-ready. It doesn't mention error handling, rate limits, or authentication needs, but covers core behavioral aspects adequately.

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 clear paragraphs: purpose, version characteristics, usage context, and output usage. Every sentence adds value, though the final sentence about output usage could be slightly more concise by combining with the previous sentence about the sibling tool.

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?

For a zero-parameter tool with no output schema, the description provides good context: what it returns (stable version in semver format), where it comes from (GitHub releases), when to use it (before upgrades), and how it connects to the sibling tool. It doesn't describe error cases or exact return structure, but covers the essential information well.

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 with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist, but it does explain the output format ('semantic versioning') and how the output relates to other tools, adding value beyond the empty schema.

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 specific action ('Gets the latest stable version'), resource ('React Native from GitHub releases'), and scope ('excludes any release candidates or beta versions'). It distinguishes from the sibling tool by specifying this tool retrieves the stable version while the sibling compares 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') and when not to use it (for non-stable versions). It names the alternative tool ('get-react-native-diff') and specifies the relationship ('must be called before calling get-react-native-diff tool').

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/rn-mcp'

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