Ceki

rent-browser

Rent a real Chrome browser session for automation. Control it via navigate, click, type, screenshot, and stop commands. Per-minute billing.

Instructions

Rent a real Chrome browser session. Returns session_id and provider info. Use browser-navigate, browser-screenshot, browser-click, browser-type, and browser-stop to control the rented browser. Per-minute billing from your AgentWallet.

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_id": "<browser_id>"
    },
    "name": "rent-browser"
  }
}

Input Schema

Name	Required	Description	Default
`browser_id`	Yes	Provider browser ID from search-browsers or list-my-browsers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 26, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description bears full burden. It discloses billing and return values (session_id, provider info) but omits authentication requirements, error handling, or limits. Adequate but not comprehensive.

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 sentences, front-loaded with primary purpose, and no wasted words. Efficient and easy to parse.

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

Completeness4/5

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

Given the tool's simplicity (1 required param, no output schema, no annotations), the description covers purpose, usage guidance, and billing. Missing details like response format or failure modes, but still reasonably complete.

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 covers 100% of parameters with a description for browser_id. The description adds no further meaning, so baseline of 3 is appropriate.

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 clearly states the action: 'Rent a real Chrome browser session.' It distinguishes from sibling control tools like browser-navigate and browser-click, which are for controlling the rented browser.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists sibling tools to use after renting, providing clear usage context. Does not mention when not to use or alternatives beyond the listed control tools, but still strong guidance.

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