Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List a device's events

list_device_events
Read-onlyIdempotent

Retrieve one device's events, such as geofence entries and exits, alarms, and shipment updates, within a chosen time window. Filter by event type, geofence, or shipment and page through results.

Instructions

List a device's events

Returns one device's events (geofence enters and exits, alarms, shipment events) within a time window: the list_events feed, scoped to one device.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Must be at least 1.
sortNoSort on event_at. Prefix with - for descending. Defaults to -event_at.
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.
event_typeNoEvent type (e.g. geofence-exit, alarm-sos, shipment-late). Repeatable. Must not be greater than 128 characters.
event_afterNoStart of the window on event_at. Defaults to 24 hours before event_before when both are omitted, or 30 days before event_before when only event_before is set. Must be a valid date.
geofence_idNoRestrict to events for one geofence. Must be at least 1.
shipment_idNoRestrict to events for one shipment. Must be at least 1.
event_beforeNoEnd of the window on event_at. Defaults to now when omitted, or 30 days after event_after when only event_after is set. Must be a valid date. Must be a date after or equal to <code>event_after</code>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that results are bounded by a time window and enumerates the event categories returned, which is useful context. It says nothing about pagination behavior or result ordering beyond what the schema documents.

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?

Two short sentences, front-loaded with the action and then the scope qualifier; there is no filler. The first line largely repeats the title, which is minor waste but keeps the definition readable.

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 9-parameter read tool whose schema is fully annotated and whose annotations cover safety, the description gives enough to select and call it correctly: resource, scope, time-window framing, and returned event kinds. Return shape is not described, but no output schema exists and the description does not need to carry that burden for a filter-list tool.

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%, so every parameter is already documented, and the description does not restate or extend per-parameter semantics. Its enumeration of event families (geofence, alarm, shipment) loosely illustrates what the event_type array accepts, which is useful but marginal. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List a device's events') and clarifies scope with 'the `list_events` feed, scoped to one device', which lets an agent separate it from the fleet-wide sibling. It also names the event families covered (geofence enters/exits, alarms, shipment events), though it does not contrast against other device-scoped siblings such as list_device_positions.

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?

Usage is implied rather than stated: the 'scoped to one device' framing hints that list_events is the alternative for fleet-wide queries, but there is no explicit 'use this when / use X otherwise' instruction. An agent can infer the choice but must do the work itself.

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