Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List groups

list_groups
Read-onlyIdempotent

Lists the account's device groups with pagination and sorting so you can find a group before retrieving its member devices.

Instructions

List groups

Lists the account's device groups. A group's devices are listed with list_group_members. Each group's page in the GPX app is https://app.gpx.co/groups/{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_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Must be at least 1.
sortNoSort column, prefixed with - for descending.
per_pageNoResults per page. Defaults to 50, capped at 100. Must be at least 1. Must not be greater than 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.4/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 two genuinely useful behavioral facts: devices are not returned here, and each group maps to a GPX app page URL. It does not describe ordering defaults, pagination termination, or what fields a group carries.

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 purpose and containing no filler. The only waste is the leading line repeating the tool title "List groups" verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple paginated list tool with full annotation coverage this is mostly adequate, but with no output schema the description never indicates what a group record contains (e.g. id, name), which the agent needs to use results. The URL template implies an `id` field but does not state it.

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%, with page, sort (including the '-' descending convention) and per_page (default 50, cap 100) all documented in the schema. The description adds no parameter-level meaning, which is acceptable at this coverage level but earns only the 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 description states a specific verb and resource: "Lists the account's device groups." It also implicitly separates itself from get_group (singular) and explicitly routes device-level data to list_group_members, so an agent can distinguish the main sibling. It stops short of a full sibling differentiation statement, but the purpose is unambiguous.

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?

One explicit routing rule is given: a group's devices come from list_group_members, not this tool. Beyond that there is no when-to-use or when-not guidance, no mention of when to prefer get_group over this list, and no pagination guidance (e.g. loop until fewer than per_page results).

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