Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List geofences

list_geofences
Read-onlyIdempotent

Retrieve an account's geofences—the named places devices enter and leave—and filter them by place type, ownership, search term, or sort order.

Instructions

List geofences

Lists the account's geofences, the named places devices enter and leave. Filterable by place type and ownership type, each multi-value. Each geofence's page in the GPX app is https://app.gpx.co/geofences/{id}.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Must be at least 1.
sortNoSort column, prefixed with - for descending.
searchNoPartial match on the geofence name. Must not be greater than 255 characters.
per_pageNoResults per page. Defaults to 50, capped at 100. Must be at least 1. Must not be greater than 100.
place_typeNoA place type slug, standard or one of the account's own. A standard slug also matches its custom types. Up to 100 values.
ownership_typeNoAn ownership type.

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. The description adds genuine context beyond that: a plain-language definition of a geofence and a URL template for linking each record to the GPX app, but it says nothing about result ordering defaults or what metadata accompanies the list.

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?

Three short sentences, front-loaded with the core action and definition, then filters, then the URL template. The only waste is the leading line restating the title verbatim, which adds nothing for an agent already given the name.

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 zero-required-parameter list endpoint with a fully described six-parameter schema and no output schema, the description covers what the tool returns and how to deep-link results. It does not explain pagination behavior or default result counts beyond what the schema states, a minor omission given the schema's completeness.

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 page, sort, search, per_page, place_type and ownership_type are all documented in the schema itself. The description only reinforces that place_type and ownership_type accept multiple values, which is marginal value over the schema's per-parameter text. Baseline 3 is appropriate when the schema carries the semantics.

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 (lists) and resource (the account's geofences) and defines the domain term as 'named places devices enter and leave', which an agent unfamiliar with geofencing would not otherwise know. It is clearly a collection endpoint, distinguishable by name from the sibling get_geofence, though it never explicitly contrasts the two.

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?

Filtering context is implied by naming the two filter dimensions (place type, ownership type) and noting each is multi-value, but there is no explicit when-to-use statement, no steering toward get_geofence for single-record retrieval, and no mention of how to page through large result sets.

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