Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Show a geofence

get_geofence
Read-onlyIdempotent

Retrieve a single geofence by ID to view its geometry, place type, ownership type, and alerting settings. Use IDs from list_geofences.

Instructions

Show a geofence

Returns one geofence with its geometry, place type, ownership type and alerting settings. The geofence's page in the GPX app is https://app.gpx.co/geofences/{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": {
      "geofenceId": "<geofenceId>"
    },
    "name": "get_geofence"
  }
}

Input Schema

NameRequiredDescriptionDefault
geofenceIdYesThe geofence id, from `list_geofences`.

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 this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds the payload contents (geometry, place type, ownership type, alerting settings) and a deep link into the GPX app, which is useful context but not deep behavioral disclosure such as error or permission behavior.

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 that lead with what is returned. The opening 'Show a geofence' merely restates the title verbatim and could be dropped, but there is otherwise no filler.

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 one-parameter read tool with no output schema, the description supplies an adequate summary of returned fields plus a direct app URL. Only minor gaps remain, such as what a missing-id failure looks like.

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% and the single geofenceId parameter is already documented as coming from list_geofences, so the schema carries the parameter burden. The description adds no syntax, format, or validation detail beyond that baseline.

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?

The verb 'Show' plus the resource 'a geofence' is specific, and 'Returns one geofence' makes clear this is a single-item fetch rather than a listing. It does not explicitly name list_geofences as the plural counterpart, but the singular/plural split is evident from the sibling names.

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 only implied: an agent can infer it should call this when it already has a geofence id and needs details. There is no explicit statement of when to prefer this over list_geofences or what happens if the id is invalid.

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