Skip to main content
Glama

open

Navigate to a URL and return a compact page snapshot with stable element IDs for AI agents to inspect and act on.

Instructions

Open URL; returns snapshot with element ids.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
modeNo
blockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions navigation and returning a snapshot with element ids, but does not explain what 'mode' or 'block' do, whether navigation waits for page load, side effects, authentication needs, or failure behavior.

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 definition is a single, front-loaded sentence with no wasted wording. It is efficient, though its extreme terseness leaves important behavior to be inferred elsewhere.

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?

For a browser navigation tool with multiple modes, no annotations, no output schema, and 0% parameter description coverage, the description is incomplete. It covers the basic action and return snapshot, but omits mode semantics, blocking behavior, and operational context needed to invoke it confidently.

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, but it only implies the meaning of 'url'. The 'mode' enum values (minimal/actions/read/full) and the 'block' boolean are not explained at all, leaving critical parameter semantics opaque.

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 action ('Open URL') and adds useful return behavior ('returns snapshot with element ids'), so the agent can understand the core operation. It does not explicitly distinguish this tool from siblings like snapshot or screenshot, which keeps it below a 5.

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 guidance on when to use this tool versus alternatives such as snapshot, act, or screenshot. There are no exclusions, prerequisites, or contextual triggers mentioned.

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