Skip to main content
Glama

Navigate the User's Preview

navigate_preview
Read-only

Point the user's OPEN Floot preview at what you built, to SHOW it to them; pair it with screenshot_preview to see it yourself. targetType "page": the app's router goes to path. "component": the component's .example.tsx for name (if it has none, say so or create one). "page-examples": the staged screens in pages/.__example.tsx (the file must exist), listing them; "#" opens one. "design": the canvas designs/.tsx fitted, listing its sections and frames; "#" zooms to one. "link-preview": the link preview card (pages/.ogImage.tsx) of the page at path, with its verdict. "merge-review": the merge review of branch projectId, into main or the branch id in name; only in the user's own signed-in window, otherwise it fails and returns a link to it. Needs a Floot window open for this project; fails fast otherwise.

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": {
      "projectId": "<projectId>",
      "targetType": "<targetType>"
    },
    "name": "navigate_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe item name as list_files shows it, no folder or extension: "HeroSection", "dashboard", "_index", "user.$id", page examples with "#<screen slug or title>" ("dashboard#empty-state"), or a design with "#<id>" ("CheckoutExplorations#payment"; "section:", "frame:" or "bookmark:" after the # when ids collide).
pathNotargetType "page" or "link-preview": a path from "/", query and hash allowed ("/user/123?tab=settings#top"; pages/user.$id.tsx serves /user/<id>).
projectIdYes
targetTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / targetType / enum
      Previous value: -[
      -  "page",
      -  "component",
      -  "page-examples",
      -  "design",
      -  "link-preview"
      -]New value: +[
      +  "page",
      +  "component",
      +  "page-examples",
      +  "design",
      +  "link-preview",
      +  "merge-review"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / path / description
      Previous value: -"targetType \"page\": a URL path from \"/\", query and hash allowed (\"/user/123?tab=settings#top\"; pages/user.$id.tsx serves /user/<id>)."New value: +"targetType \"page\" or \"link-preview\": a path from \"/\", query and hash allowed (\"/user/123?tab=settings#top\"; pages/user.$id.tsx serves /user/<id>)."
    • changedInput schema / properties / targetType / enum
      Previous value: -[
      -  "page",
      -  "component",
      -  "page-examples",
      -  "design"
      -]New value: +[
      +  "page",
      +  "component",
      +  "page-examples",
      +  "design",
      +  "link-preview"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The item name as list_files shows it, no folder or extension: \"HeroSection\", \"dashboard\", \"_index\", \"user.$id\", or a design with \"#<id>\" (\"CheckoutExplorations#payment\"; \"section:\", \"frame:\" or \"bookmark:\" after the # when ids collide)."New value: +"The item name as list_files shows it, no folder or extension: \"HeroSection\", \"dashboard\", \"_index\", \"user.$id\", page examples with \"#<screen slug or title>\" (\"dashboard#empty-state\"), or a design with \"#<id>\" (\"CheckoutExplorations#payment\"; \"section:\", \"frame:\" or \"bookmark:\" after the # when ids collide)."
  4. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The item name without folder prefix or extension, exactly as list_files shows it. For targetType \"component\" a component — e.g. \"HeroSection\". For targetType \"page-examples\" a page — e.g. \"dashboard\", \"_index\", \"user.$id\". For targetType \"design\" a design, optionally with \"#<section, frame or bookmark id>\" — e.g. \"CheckoutExplorations#payment\" (prefix \"section:\", \"frame:\" or \"bookmark:\" after the # when ids collide)."New value: +"The item name as list_files shows it, no folder or extension: \"HeroSection\", \"dashboard\", \"_index\", \"user.$id\", or a design with \"#<id>\" (\"CheckoutExplorations#payment\"; \"section:\", \"frame:\" or \"bookmark:\" after the # when ids collide)."
    • changedInput schema / properties / path / description
      Previous value: -"For targetType \"page\": the URL path to navigate to, starting with \"/\" — query and hash allowed, e.g. \"/user/123?tab=settings#top\"."New value: +"targetType \"page\": a URL path from \"/\", query and hash allowed (\"/user/123?tab=settings#top\"; pages/user.$id.tsx serves /user/<id>)."
  5. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The item name without folder prefix or extension, exactly as list_files shows it. For targetType \"component\" a component — e.g. \"HeroSection\". For targetType \"page-examples\" a page — e.g. \"dashboard\", \"_index\", \"user.$id\"."New value: +"The item name without folder prefix or extension, exactly as list_files shows it. For targetType \"component\" a component — e.g. \"HeroSection\". For targetType \"page-examples\" a page — e.g. \"dashboard\", \"_index\", \"user.$id\". For targetType \"design\" a design, optionally with \"#<section, frame or bookmark id>\" — e.g. \"CheckoutExplorations#payment\" (prefix \"section:\", \"frame:\" or \"bookmark:\" after the # when ids collide)."
  6. Changed1 schema field changed
    • changedInput schema / properties / targetType / enum
      Previous value: -[
      -  "page",
      -  "component",
      -  "page-examples"
      -]New value: +[
      +  "page",
      +  "component",
      +  "page-examples",
      +  "design"
      +]
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/destructive/openWorld annotations by disclosing failure conditions: no open Floot window means fast failure, and merge-review requires the user's signed-in window but degrades gracefully by returning a link. It does not describe what a successful call returns or how navigation behaves over time, so a 4 rather than 5.

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?

Front-loads the core action and the sibling pairing, then enumerates modes compactly with no filler. The dense quoting and semicolon chains make it harder to scan than it needs to be, costing a point.

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?

Covers all six modes, failure modes, and the merge-review fallback with no output schema to lean on. It omits what a successful navigation returns or confirms, which is the one gap for a tool with four parameters and no response schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only enumerates targetType; the description defines what each of the six modes means and how name/path are interpreted per mode (e.g. "#<screen>" opens one, "#<id>" zooms to a frame). This adds substantial meaning beyond the 50% schema coverage.

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?

States a concrete verb and resource ("Point the user's OPEN Floot preview at what you built") and immediately contrasts itself with the sibling screenshot_preview. The six targetType values further pin down exactly what it can act on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the intent ("to SHOW it to them") and pairs itself with screenshot_preview for the agent's own viewing, which is real routing guidance. It stops short of explicit when-not-to-use criteria or naming other alternatives, so it is not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources