Skip to main content
Glama
Sign In
FoxBridge MCP

FoxBridge MCP

by sinamohsenifar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate

Navigate the active browser tab to a specified URL and retrieve page data, with optional use of a profile to preserve cookies and sessions.

Instructions

Navigate the active tab to a URL and return it as data. Set useProfile to a profile name (or "" for default) to use a COPY of your real cookies/sessions; omit for a clean browser.

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": {
      "url": "<url>"
    },
    "name": "navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
useProfileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Vague on return value ('it as data'), no mention of page load completion, error handling, or state changes beyond profile usage. Insufficient for an operation that modifies browser state.

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?

Two sentences, front-loaded with primary action, no filler. Every word serves a purpose.

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?

No output schema, so return value needs explanation. Does not specify what 'return it as data' means (URL only? page content?). Missing details on when to use this vs sibling tools like ff_navigate or open_tab. Incomplete for effective use.

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 0% but description adds meaning: url is the target, useProfile specifies profile usage. Explains 'omit for a clean browser' and 'set to a profile name or empty string for default', which is helpful beyond raw 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?

Clearly states verb 'navigate', resource 'active tab', and outcome 'return it as data'. Distinguishes from siblings like open_tab (opens new tab) and ff_navigate (Firefox-specific).

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

Usage Guidelines3/5

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

Explains useProfile parameter for session handling but fails to differentiate when to use navigate vs other browser navigation tools (e.g., ff_navigate, open_tab). No explicit when-not or alternatives given.

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