Skip to main content
Glama

app_reload

Reload the JavaScript bundle of a live Expo app to apply code changes, replicating the Metro 'r' key action.

Instructions

Reload the JS bundle (like pressing r in Metro).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden. 'Reload the JS bundle' implies in-process state loss and a possible return to the initial route, but none of that is disclosed, nor is any requirement for the Metro dev server to be running. The only real disclosure is the narrowing to the JS bundle rather than native code.

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?

A single short sentence with the action front-loaded and no filler; the parenthetical analogy earns its place by disambiguating the verb. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool this is nearly sufficient, but with no annotations and no output schema the description should still say what the caller observes afterward (bundle reload, state reset) and any dev-server precondition. Those omissions are meaningful for a state-altering action.

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 takes zero parameters, and the schema has nothing to document, so the baseline of 4 applies. The description adds a useful analogical explanation of the action instead of leaving the empty schema uninterpreted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Reload the JS bundle'), and the Metro 'r' analogy pins down exactly what kind of reload is meant — a dev-server bundle refresh, not an app restart. It does not need to differentiate from siblings like app_tap or app_navigate, which are plainly unrelated, but it never says how it differs from a full relaunch, which keeps it just below a 5.

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?

There is no statement of when to call this (e.g., after shipping JS changes) or when not to (e.g., when native code changed and requires a full rebuild). The Metro analogy describes the mechanism, not the selection criteria, so the agent must infer timing from context.

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