Skip to main content
Glama

app_navigate

Opens Expo Router paths or deep links to move a live app to a specific screen for recording, testing, or guided navigation.

Instructions

Open a route (expo-router path like "/settings") or a full deep link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "app_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNofull screen instead of a diff
pathYes
replaceNoreplace the current screen instead of pushing (keeps the stack shallow)
snapshotNoreport the screen afterwards (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 full behavioral burden. It does not say whether navigation is destructive to the existing stack, what happens on an invalid path, whether auth/session state matters, or what the caller receives after navigating — all relevant for a mutation-like UI action.

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?

A single sentence, front-loaded with the action and immediately followed by the accepted path format. It is appropriately sized, though the parenthetical is doing most of the explanatory work and could have been paired with one sentence on stack behavior.

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?

With four parameters, no output schema, and no annotations, the description is thin for a navigation tool that alters app state. Missing are stack/replace implications, failure behavior for bad routes, and any indication of what the caller gets back after the screen changes.

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 description coverage is 75%, so most parameters are already documented in the schema. The description adds a useful clarification of the path format (expo-router style like '/settings') and hints at the full deep-link mode, but it does not explain replace, full, or snapshot semantics beyond what the schema text already says.

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?

The description states a concrete verb and resource ('Open a route ... or a full deep link') and gives a concrete path example ('/settings'), so an agent knows this triggers in-app navigation. It does not explicitly distinguish itself from siblings such as app_reload or app_snapshot, which keeps it short of 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 guidance on when to prefer this tool over siblings (e.g., app_reload for reloading, app_snapshot for inspecting the current screen) and no exclusions. It also does not say when to choose a route path versus a full deep link, leaving the key selection decision to the agent.

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