Set the geolocation reported by navigator.geolocation to test region-specific behavior, or auto-resolve coordinates from the proxy exit IP.
Set the geolocation reported by navigator.geolocation. Pass fromProxyIp=true to auto-resolve from proxy exit IP.
| Name | Required | Description | Default |
|---|---|---|---|
| accuracy | No | ||
| latitude | No | ||
| longitude | No | ||
| fromProxyIp | No | If true, resolve geolocation from the configured proxy's exit IP via cloak's geoip backend. |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses the target surface (navigator.geolocation) but says nothing about persistence, whether the setting survives navigation, permission requirements, or interaction with the proxy. For an unannotated mutation tool this is a significant gap.
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?
Two compact sentences, front-loaded with the primary effect followed by the proxy shortcut. Efficient, though the second sentence duplicates schema content.
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?
A mutation tool with zero annotations, no output schema, and 3 of 4 parameters undocumented. The description should explain persistence and proxy interaction but does not, leaving the agent under-informed.
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 coverage is only 25% (just fromProxyIp). The description restates the fromProxyIp semantics already present in the schema and adds no meaning for latitude, longitude, or accuracy. It does not compensate for the low coverage.
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+resource ('Set the geolocation reported by navigator.geolocation'), making the effect precise. It does not, however, explicitly differentiate itself from sibling setters like cloak_set_timezone, cloak_set_locale, or cloak_set_fingerprint.
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?
Gives one conditional hint (pass fromProxyIp=true to auto-resolve from proxy exit IP), which is implied usage rather than explicit when-to-use/when-not. No guidance on when to prefer explicit lat/long versus proxy-derived geolocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.