Skip to main content
Glama
Sign In
dawg-mcp

dawg-mcp

by dawgswarm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browser_provision

Provision a remote stealth browser with optional proxy and geolocation, returning a session ID and initial snapshot for automated web control.

Instructions

Provision a remote stealth Chromium and connect to it.

Args: proxy: Optional proxy URL, e.g. "socks5://user:pass@host:port". geo: Optional geolocation — a city slug (e.g. "moskva") or "lat,lon" coordinates (e.g. "55.75,37.61").

Returns session_id (pass it to other browser_* tools), browser_id, the current url/title, and an initial AI snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_provision"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxyNo
geoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the action and return values, but does not disclose potential costs, resource limits, or side effects of provisioning a browser.

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?

Concise, well-structured with Args section; every sentence is necessary and front-loaded with the main action.

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?

Covers purpose, parameters, and return values. Does not specify browser lifecycle or error scenarios, but for a provisioning tool this is adequate given sibling tools handle release.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds essential meaning for both parameters—proxy URL format and geo formats (city slug or coordinates) with examples.

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?

'Provision a remote stealth Chromium and connect to it' uses a specific verb and resource, and clearly distinguishes from sibling browser tools that operate on an existing session.

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 states that the returned session_id should be passed to other browser_* tools, implying this is used first. However, no explicit when-not-to-use or alternatives are given.

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