Skip to main content
Glama

set_location

Simulate a device GPS position by setting latitude and longitude to test location-based flows on iOS and Android phones, tablets, and foldables; TV devices are unsupported.

Instructions

Set the device's simulated GPS location, for location-based flows. Phones, tablets and foldables (iOS and Android); not available on TV devices.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "set_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees, -90 to 90.
longitudeYesLongitude in decimal degrees, -180 to 180 (west is negative).
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description's addition of "simulated" is valuable: it tells the agent this spoofs GPS rather than changing real device configuration. It also adds a platform-availability constraint the annotations cannot express. Remaining gaps are persistence across sessions and whether a running session is mandatory, though the session_id schema partially covers the latter.

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 compact sentences with the core action front-loaded and the platform caveat trailing. No wasted clauses, no restating of the tool name.

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?

For a simple 3-parameter device-state mutation with a fully documented schema and no output schema, the description covers purpose, simulation semantics, and platform scope. It could be more complete by noting whether the simulated location persists until changed or resets on session end.

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 coverage is 100%, and the schema already documents latitude/longitude ranges, the west-is-negative convention, and the session_id fallback chain. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 pairs a specific verb ("Set") with a specific resource ("the device's simulated GPS location"), which is immediately distinguishable from sibling setters like set_language, set_posture, or set_status_bar that target different device attributes.

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?

"For location-based flows" gives a concrete usage context, and the platform restriction explicitly states a when-not case ("not available on TV devices"). It stops short of naming an alternative tool or fallback once the device is excluded, but no obvious sibling substitute exists in the catalog.

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