Override device GPS coordinates to test location-based features or simulate different regions. Set latitude, longitude, and accuracy for browser automation.
Override device GPS geolocation coordinates (latitude, longitude, accuracy).
| Name | Required | Description | Default |
|---|---|---|---|
| accuracy | No | Accuracy in meters | |
| latitude | Yes | Latitude coordinate | |
| longitude | Yes | Longitude coordinate |
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It says nothing about whether the override requires a page reload to take effect, whether it persists across navigations or session end, whether location permissions must first be granted (see browser_grant_permissions), or whether it is reversible. For a state-mutating spoofing tool with zero annotation coverage, these are meaningful gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that names the action, the target, and the fields. No wasted words and no buried information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description is the sole source of behavioral context, yet it omits persistence scope, reload requirements, and permission dependencies. For a browser-state mutation tool this leaves the agent under-informed about side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so latitude, longitude, and accuracy are already documented in the schema, including the accuracy unit and default. The description only restates the parameter names, adding no syntax or semantics beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Override') and resource ('device GPS geolocation coordinates') and enumerates the three fields it touches. It is distinguishable from related siblings like browser_set_timezone and browser_set_user_agent, though it never names them explicitly to reinforce the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus browser_emulate_environment or browser_set_timezone, nor any stated prerequisites. The agent must infer from the name alone that this is for spoofing location during browser automation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.