Skip to main content
Glama
Sign In
AginxBrowser

AginxBrowser

by yinnho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

session_navigate

Navigate an active browser session to a new URL by providing the session ID and target URL.

Instructions

Navigate a browser session to a new URL.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
session_idYesSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • removedInput schema / title
      Removed value: -"SessionNavigateParams"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses the core behavior—navigation to a URL—which is the main observable effect. However, annotations provide only a title, so the description carries the full burden of behavioral disclosure and does not mention whether the tool waits for page load, how it handles invalid URLs, or whether it returns after navigation.

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, compact sentence that front-loads the verb and target resource. Every word is necessary, and there is no filler or redundant context.

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

Completeness3/5

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

For a simple two-parameter action, the schema covers the parameters completely, and the description gives the essential operation. Still, without an output schema and without behavioral annotations, an agent lacks return-value and postcondition context that would make the tool fully self-sufficient.

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?

The input schema already fully documents both parameters with descriptions: 'URL to navigate to' and 'Session ID'. The description repeats the URL concept without adding any additional meaning, so it stays at the baseline for 100% 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?

The description states a specific action—'navigate'—against a specific resource, a browser session, and clarifies the target is a URL. This is clear enough to distinguish session_navigate from sibling tools like session_click, session_eval, or session_wait.

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 provides no guidance on when to use this tool instead of alternatives. It neither mentions prerequisites, such as an active session, nor contrasts itself with closely related siblings like fetch, click, or session_wait that could also change a browser's state.

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