Skip to main content
Glama

open_page

Opens a URL or local file path in a browser, returning page metadata, final URL, HTTP status, and viewport dimensions to support inspection and responsive testing.

Instructions

Open a URL or local file path in the browser and return page metadata, final URL, HTTP status, and viewport dimensions.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL or file path to open (e.g. "https://example.com" or "C:/sites/index.html")
timeoutNoMaximum timeout in ms (default: 30000ms).
wait_untilNoWait until condition ("domcontentloaded", "load", "networkidle", "commit"). Default is "domcontentloaded".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/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 usefully discloses the return payload (page metadata, final URL, HTTP status, viewport dimensions), which implicitly reveals that redirects are followed and failures are reported, but it says nothing about whether a new tab or the current page is used, whether existing page state is lost, or what happens when the timeout expires.

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?

A single front-loaded sentence with the action first and the return values second; there is no redundant or filler wording.

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?

With no output schema, the description correctly takes on the job of describing return values, and the schema covers all parameters. However, with zero annotations, the definition is still silent on side effects and session/tab behavior, which matters for a tool that mutates browser state.

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 100%, with per-parameter descriptions, defaults, and an enum for wait_until, so the schema already does the heavy lifting. The description adds no additional meaning about url, timeout, or wait_until beyond what the schema states; baseline 3 applies.

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?

States a specific verb and resource: "Open a URL or local file path in the browser," which clearly separates it from sibling navigation tools like navigate_back, navigate_forward, and reload_page, none of which take an arbitrary URL. It stops short of naming any sibling explicitly, so 4 rather than 5.

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?

The description implies when the tool applies (loading a URL or local file into the browser) but gives no explicit when-to-use vs when-not guidance and never mentions alternatives such as reload_page or inspect_page. An agent must infer the routing decision from the sibling names alone.

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