Skip to main content
Glama

lease

Take or renew exclusive access to a signed-in Chrome browser session and get its DevTools endpoint; if busy, use another browser or retry later.

Instructions

Take the browser for this session, or renew your lease (the same session and endpoint). Returns the DevTools endpoint to connect your driver to. BUSY: another agent holds it; use another browser or try later. minutes: the lease length, up to the configured maximum.

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": {
      "browser": "<browser>"
    },
    "name": "lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserYes
minutesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses exclusivity via BUSY, renewal semantics, and the maximum lease length, but it omits lease expiry behavior, release expectations, and any permission or lifecycle details.

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 front-loaded and contains little fluff: purpose, return value, BUSY behavior, and minutes semantics are each addressed briefly. Some details are densely packed but remain readable.

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?

The presence of an output schema means return values need less explanation, and the description covers key behaviors like BUSY and renewal. Still, the required 'browser' parameter and lease lifecycle are under-specified for a tool with 0% schema parameter coverage.

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 explains 'minutes' as lease length up to a configured maximum, but it does not describe the required 'browser' parameter at all, leaving accepted values or selection semantics unclear.

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 and resource: taking the browser for this session or renewing the lease. It is distinguishable from status/release by the verbs 'take' and 'renew', but it does not explicitly name or contrast with siblings.

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?

It gives useful context for acquiring or renewing a lease and explains the BUSY condition with fallback actions. However, it does not explain when to use release or status instead, leaving lifecycle guidance implicit.

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