Skip to main content
Glama

floot

by com.floot
OverviewDiscussionsAdmin

Navigate the User's Preview

navigate_preview
Read-only

Point the user's OPEN Floot preview at a page URL, a component's examples, or a page's examples — use it to SHOW the user what you just built ("here's the new dashboard page", "here's the Button component's states"), and pair it with screenshot_preview to see the result yourself. targetType "page" navigates the app's router to path — a URL path with optional query/hash ("/", "/user/123?tab=settings#top"; pages/user.$id.tsx serves /user/). targetType "component" renders the component's .example.tsx showcase for name ("HeroSection", exactly as list_files shows it; tell the user if it has no example — you can create one). targetType "page-examples" renders the staged screens in pages/.__example.tsx for the page name ("dashboard", "_index") — the same view as the preview's Live/Examples switch, so it needs that file to exist. targetType "design" shows the design canvas designs/.tsx for name ("CheckoutExplorations"), fitted to all frames, and lists its sections and frames; append "#" to zoom to one section, frame or bookmark ("CheckoutExplorations#payment"), like opening one screen of a page's examples. Requires a Floot window to be open for this project; fails fast with guidance when none answers. Does not modify the project.

Input Schema

NameRequiredDescriptionDefault
nameNoThe 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).
pathNoFor targetType "page": the URL path to navigate to, starting with "/" — query and hash allowed, e.g. "/user/123?tab=settings#top".
projectIdYes
targetTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)."
  2. Changed1 schema field changed
    • changedInput schema / properties / targetType / enum
      Previous value: -[
-  "page",
-  "component",
-  "page-examples"
-]New value: +[
+  "page",
+  "component",
+  "page-examples",
+  "design"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it requires an open Floot window, fails fast with guidance when none answers, and does not modify the project. It also explains what each target type renders, though some details (e.g., exact failure behavior) remain light. Annotations already cover safety, so this is a strong addition.

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?

The description is front-loaded with the core action and then provides detailed target-specific guidance. It is dense but mostly earns its length through concrete examples and edge-case details; some parenthetical examples could be trimmed.

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

Completeness5/5

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

With no output schema and only partial schema descriptions, the description provides enough context for an agent to call the tool correctly: it covers prerequisites, failure behavior, target-type semantics, and the handoff to screenshot_preview. Nothing essential is missing.

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?

Schema coverage is 50%, but the description compensates well by explaining targetType values and the meaning of path and name, including examples and router behavior. The projectId parameter is not described in the text, but its role is self-evident from the name.

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 uses a specific verb and resource: 'Point the user's OPEN Floot preview at...' and distinguishes four target types with concrete examples. It clearly separates this from screenshot_preview by explaining it is for showing the user, while screenshot_preview is for seeing the result yourself.

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?

It gives a clear primary use case ('use it to SHOW the user what you just built') and pairs it with screenshot_preview for verification. However, it does not explicitly state when not to use this tool or give conditions for choosing between all alternatives, so it stops short of a full 5.

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

All floot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources