Skip to main content
Glama
Sign In
React Native MCP Server

React Native MCP Server

by MrNitro360
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_version_info

Obtain the current version and optional build details of the React Native MCP Server.

Instructions

Get React Native MCP Server version and build information

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

Input Schema

NameRequiredDescriptionDefault
include_build_infoNoInclude detailed build information

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The description implies a read-only operation (getting information), but does not explicitly state that it has no side effects or that it is safe to call repeatedly. With no annotations provided, this lack of explicit disclosure limits transparency.

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?

The description is a single, clear sentence with no extraneous words. It effectively communicates the tool's purpose without unnecessary detail.

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 simple retrieval tool with one optional parameter and no output schema, the description adequately states what information is returned. It could be slightly improved by noting that the operation is safe and instantaneous.

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% for the single boolean parameter 'include_build_info', which already has a clear description. The tool description adds no further meaning beyond what the schema provides, resulting in a baseline score.

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?

Description clearly states that the tool retrieves version and build information for the React Native MCP Server. The verb 'Get' and the specific resource distinguish it from all sibling tools, none of which appear to provide version info.

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 or why to use this tool, nor any mention of alternatives. While it's a straightforward version retrieval, the description does not caution about frequency or prerequisites.

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