Skip to main content
Glama

privacy_session_open

Open a URL in a privacy session while enforcing login, CAPTCHA, and paywall controls; blocked access stops the session and is never bypassed.

Instructions

Open a URL inside a privacy session. Access controls are still enforced - a login, CAPTCHA or paywall stops the session, it is never bypassed.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose a genuinely non-obvious behavioral trait: access controls are enforced, and a login, CAPTCHA or paywall terminates the session rather than being bypassed. What it omits is the failure mode — whether the tool errors, returns a status, or leaves the session in a terminal state — and there is no output schema to fill that gap.

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?

Two short sentences, purpose front-loaded, and the second sentence delivers a caveat that materially changes how an agent should plan the call. Nothing is redundant.

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 tool with no annotations and no output schema, the description covers what it does and the main policy constraint. It stops short of covering prerequisites (obtaining a session_id) and the observable outcome when a login, CAPTCHA or paywall interrupts the navigation, which are the two things an agent most needs to handle this correctly.

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% on two required parameters, so the description must compensate and largely does not. 'A URL' loosely signals what url accepts, and 'a privacy session' loosely signals what session_id refers to, but neither format, provenance, nor validation expectations are clarified.

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 object ('Open a URL') plus the container it operates in ('inside a privacy session'), which separates it from the session lifecycle siblings. It does not explicitly distinguish itself from the similarly-named navigation sibling body_open_external, so the sibling differentiation is only partial.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The required session_id implies a session must already exist (presumably via privacy_session_start), but the description never states that prerequisite or explains why an agent would pick this over body_open_external.

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