Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List a device's positions

list_device_positions
Read-onlyIdempotent

Retrieve a device's recorded positions within a specified time window, 24 hours by default, to review where it has been.

Instructions

List a device's positions

Returns the positions a device recorded within a time window, 24 hours by default. Use it for where a device has been; for where it is now, use get_device with include=last_position.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Must be at least 1.
sortNoSort on location_at, prefixed with - for descending.
deviceIdYesThe device id, from `list_devices`.
per_pageNoResults per page. Defaults to 50, capped at 100. Must be at least 1. Must not be greater than 100.
location_afterNoStart of the window on the time the device recorded the fix. Defaults to 24 hours before location_before. Must be a valid date.
location_beforeNoEnd of the window on the time the device recorded the fix. Defaults to now. Must be a valid date. Must be a date after or equal to <code>location_after</code>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds that retrieval is time-windowed with a 24-hour default, but that default is also spelled out in the schema, and it says nothing about result volume, pagination cost, or ordering behavior beyond what the schema already documents.

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 sentences, no padding, with the historical scope front-loaded before the disambiguation. Nothing repeats the title verbatim without adding information.

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 six-parameter, read-only list tool with fully described schema and no output schema, the description covers purpose, scope, and sibling routing. The only shortfall is that it does not hint at the shape of returned position records, which matters slightly since no output schema exists.

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 description coverage is 100%, including defaults, caps, enum sort values, and the location_after <= location_before constraint, so the schema carries parameter meaning. The description only gestures at "a time window" without adding format, timezone, or filter semantics beyond what is already documented.

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 states a specific verb and resource ("List a device's positions") and immediately clarifies the semantics: positions recorded within a time window. It also explicitly separates this from the sibling get_device last-position path, so an agent can choose between them without reading 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 Guidelines5/5

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

It gives both sides of the routing decision: use this for history ("where a device has been") and get_device with include=last_position for current location. That is an explicit when-to-use plus a named alternative.

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