Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List a group's members

list_group_members
Read-onlyIdempotent

Retrieve a paginated list of devices that belong to a specified group by group ID, with optional page and per-page controls.

Instructions

List a group's members

Phase 1 groups are device-only, so every member carries type "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": {
      "groupId": "<groupId>"
    },
    "name": "list_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Must be at least 1.
groupIdYesThe group id, from `list_groups`.
per_pageNoMembers 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.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context that all members currently have type "device", which tells the agent what to expect in the payload. It says nothing about pagination behavior or result ordering 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines with the purpose front-loaded and no redundant wording. The "Phase 1" phrasing is slightly internal jargon, but it is compact and does not bloat the definition.

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 read-only list tool with a fully documented schema and clear annotations, the description is adequate but thin. With no output schema, it does not hint at what member fields are returned, which would help an agent plan the follow-up call to get_device.

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 schema itself documents groupId provenance, page numbering, and per_page defaults/caps. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 first line states a specific verb and resource (list a group's members) that clearly separates it from list_groups and get_group. It does not, however, contrast with list_devices, which returns the same entity type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this versus list_devices or get_group, and no mention of prerequisites such as obtaining groupId first. The agent must infer usage from the name and schema.

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