Skip to main content
Glama
Sign In
Free Codin Agent

Free Codin Agent

by office233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chrome_navigate

Destructive

Directs a browser tab to an http(s) URL and waits for page load, enabling automated navigation in web testing or scraping tasks.

Instructions

Navigate a tab to an http(s) URL and wait for it to load.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
tabIdNoChrome tab id (default: active tab)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already disclose that this is a non-readonly, open-world, non-idempotent, destructive operation. The description adds that the call waits for the page to load, which is useful beyond the annotations, but it does not explain what navigation may disrupt, error behavior, or timeout handling.

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?

The description is a single front-loaded sentence with no wasted words. It immediately states the action, target, and loading behavior.

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?

For a simple navigation tool with annotation coverage and no output schema, the description provides the essential action and wait condition. It is mostly complete, though it could better distinguish itself from browser_navigate and mention any timeout or failure behavior.

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 50%, and while tabId is documented in the schema, the url parameter has no schema description. The description partially compensates by constraining url to http(s) URLs, but it does not otherwise clarify expected format, redirect behavior, or tabId defaulting.

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 specific verb ('Navigate') and resource ('a tab to an http(s) URL'), and adds the loading condition. It does not distinguish this tool from the similarly named browser_navigate sibling, which is a noticeable gap.

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?

The description gives no indication of when to use chrome_navigate instead of alternatives such as browser_navigate, chrome_switch_tab, chrome_new_tab, or chrome_close_tab. Usage is only implied by the verb 'Navigate'.

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