Skip to main content
Glama
Sign In
React Native Expo MCP

React Native Expo MCP

by Divagnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

eas_update_status

Check the status of published OTA updates for Expo React Native apps, with optional branch filtering and result limits.

Instructions

Check status of published OTA updates

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

Input Schema

NameRequiredDescriptionDefault
branchNoFilter by branch name
limitNoNumber of updates to show (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states 'Check status' with no details on return format, pagination, or whether it is a read-only operation, leaving significant gaps.

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 sentence with no unnecessary words, front-loading the purpose clearly.

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?

The description fails to mention that the tool likely returns a list of updates with statuses or how it interacts with pagination (limit parameter). Given no output schema, more context on the return value is needed for completeness.

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?

Both parameters (branch and limit) are fully described in the input schema (100% coverage). The description adds no extra meaning beyond what is already in the 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 'Check status of published OTA updates' uses a specific verb and resource, clearly distinguishing from sibling tools like eas_update (create updates) and eas_build_status (build status).

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, such as when to use eas_update_status instead of eas_build_status or eas_update.

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