Skip to main content
Glama
Sign In
Asklear Browser MCP

Asklear Browser MCP

Official
by Asklear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

navigate

Direct the local Chrome browser to a specified URL, ensuring all page data remains on your machine.

Instructions

Run the local Chrome browser navigate operation. Page results stay local to the Agent.

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
request_idNo
session_idNo
visibilityNosilent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Page results stay local to the Agent' which hints at scoping, but it does not disclose effects like loading a new page, potential delays, or whether it is a read-only or mutating action in the browser context.

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 concise, two sentences, and front-loads the main action. It wastes no words, but could include more useful information without becoming verbose.

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?

Given there are 4 parameters, no annotations, and no output schema, the description is incomplete. It does not explain the meaning of the optional parameters, the significance of 'visibility', or what 'stay local' means for the agent. More context is needed for reliable use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It does not explain the purpose of 'visibility', 'session_id', 'request_id', or the format of 'url'. The description adds no parameter-level detail beyond the schema.

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 clearly states the tool performs a 'navigate operation' on the local Chrome browser, and distinguishes itself from siblings like click, fill, and observe. It could be more explicit that it is used to change the current page, but it is adequate.

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 does not provide guidance on when to use navigate versus other tools like extract or observe. It also does not specify any prerequisites or contexts where navigation is appropriate or inappropriate.

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