Skip to main content
Glama
Sign In
GPX MCP Server

GPX MCP Server

by gpxco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List users

list_users
Read-onlyIdempotent

Retrieve a paginated, sortable list of user accounts with account-scoped permission details, including explicit device and group ID grants.

Instructions

List users

Every row carries the account-scoped permission structure. permissions.device_ids and permissions.group_ids are the explicit direct grants only, not the resolved fleet the user can see.

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

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: permissions.device_ids and permissions.group_ids are direct grants only, not the resolved visible fleet — a semantic detail that would otherwise cause misreads of the returned data. It stops short of describing pagination or default ordering, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The leading "List users" line duplicates the title and earns nothing, while the second paragraph is dense and useful. Front-loading the permission-field caveat would have been stronger than opening with a restated name.

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?

There is no output schema, so the description carries the burden of describing the return shape; it correctly discloses the permission field semantics but says nothing about response envelope, total counts, or pagination metadata. For a simple three-parameter read tool this is adequate but leaves real gaps for an agent interpreting results.

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, and per_page all documented including the sort enum values and the 100 cap. The description adds nothing about parameters, which is acceptable given the schema does the full job, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List users" states a verb and resource, but the opening line is effectively a restatement of the tool name and title, adding no specificity. There is no differentiation from siblings such as get_user or list_group_members, so the agent must infer the distinction from naming conventions alone.

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?

The description gives no when-to-use guidance, no exclusions, and does not point to get_user for fetching a single account or to list_group_members for membership queries. Usage is only implied by the tool name.

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