Skip to main content
Glama
Sign In
mobile-simulator-emulator-mcp

mobile-simulator-emulator-mcp

by gitsoufiane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Mobile Location

mobile_set_location
Idempotent

Set simulated latitude and longitude on iOS Simulators and Android Emulators. Clear the location on iOS only.

Instructions

Set simulated latitude/longitude on iOS or Android. Clearing the simulated location is supported on iOS only.

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": "mobile_set_location"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
actionYes
deviceYes
latitudeNo
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds platform support details (iOS/Android, clearing on iOS) but lacks information on side effects, permissions, or state changes beyond the setting action.

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?

Description is a single concise sentence plus a brief note, with no wasted words.

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

Completeness2/5

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

Despite having an output schema (content unknown), the description is minimal. It does not explain how to specify latitude/longitude, prerequisites, or output interpretation, leaving significant gaps for a mutation tool.

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

Parameters4/5

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

Input schema has 0 parameters, so description cannot add parameter-level meaning. Baseline score of 4 is appropriate as per guidelines for zero-parameter tools.

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 tool sets simulated latitude/longitude on iOS or Android, specifying the verb 'Set' and resource. It also notes a platform-specific capability (clearing on iOS), distinguishing it from sibling tools like mobile_set_permission.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It only mentions clearing support on iOS, but no context for choosing this tool over other mobile tools.

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