Swipium

Overview Schema Source Related Servers Discussions Admin

Set location

qa_geolocation

Idempotent

Spoof GPS coordinates on Android emulators to test location-dependent app flows, with consent-gated changes logged as environment changes.

Instructions

Spoof the GPS location (Android Emulator only; consent-gated, logged as an environment change).

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": {
      "sessionId": "<sessionId>",
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "qa_geolocation"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Latitude in decimal degrees.
`lng`	Yes	Longitude in decimal degrees.
`approve`	No
`consentId`	No
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, closed-world behavior. The description adds real value beyond that by disclosing the consent gate and that the action is logged as an environment change — an audit-trail fact annotations cannot convey. However, it does not explain what the consent gate requires (how approve/consentId are used) or what happens if consent is absent.

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?

A single compact sentence that front-loads the action and then the constraints in parentheses. Nothing is wasted and the platform restriction is not buried.

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

Completeness3/5

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

For a 5-parameter mutation with no output schema and no annotations covering consent, the definition covers the platform scope and audit logging but leaves the consent workflow opaque. An agent would need to guess at approve/consentId semantics before it could safely invoke this.

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

Parameters2/5

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

Schema description coverage is only 40%: lat and lng are documented in the schema, but sessionId, approve, and consentId are undocumented. The phrase 'consent-gated' hints that approve/consentId relate to consent but does not say which is required, how a consentId is obtained, or what approve toggles — so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Spoof') with a specific resource ('GPS location'), and adds a platform scope ('Android Emulator only') that immediately frames where it applies. An agent can tell this is a location-mocking action rather than a device-info or network-inspection read.

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

Usage Guidelines3/5

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

The description supplies one hard precondition ('Android Emulator only') and notes consent gating, which is implied usage guidance. It never states when to prefer this over alternatives or when not to call it (e.g., on iOS or physical devices), so guidance is implied rather than explicit.

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