Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Show a device

get_device
Read-onlyIdempotent

Retrieve a device by ID to view its status, sharing link, container type, and optionally current position or telemetry such as battery, speed, and movement.

Instructions

Show a device

Returns one device with its status, sharing link and container type. include=last_position adds where it is now, and include=telemetry its battery, speed and whether it is moving. The device's page in the GPX app is https://app.gpx.co/trackers/{id}.

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": {
      "deviceId": "<deviceId>"
    },
    "name": "get_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoInclude telemetry and/or last_position. Comma-separate values. Omitted by default because both are cross-store reads.
deviceIdYesThe device id, from `list_devices`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description rightly focuses on what is returned: a device plus its status, sharing link and container type, with the extra fields each include unlocks. The app URL is a small bonus but also padding; there is no mention of pagination or what happens for an unknown id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the return shape, then the two optional includes. The opening line duplicates the title verbatim and the deep-link URL is marginally useful, but nothing is confusingly ordered or wasteful enough to penalize heavily.

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?

With no output schema, the description carries the burden of describing return values and does so concretely for both the default and expanded cases, which is the critical gap for a get-by-id tool. Missing only edge behavior (unknown id, whether telemetry is expensive to fetch) to be fully complete.

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%, so baseline is 3. The description does add real meaning by spelling out the payload each enum value unlocks (location now vs. battery/speed/motion), which the schema's bare "Include telemetry and/or last_position" does not, but it doesn't add format or cost details beyond that.

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?

States a specific verb and resource ("Show a device") and immediately scopes it to a single record, returning status, sharing link and container type. That single-vs-collection framing is enough to distinguish it from list_devices without opening either schema.

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?

Explains when to add each `include` value (last_position for current location, telemetry for battery/speed/motion), which is the main call-shaping decision. It doesn't explicitly name list_devices as the alternative for multiple devices, though the schema's deviceId description points back to it.

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