Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_user_group_members

Lists members of a MODX user group by group ID, with optional limit and start parameters for pagination.

Instructions

List members of a user group.

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": {
      "usergroup": "<usergroup>"
    },
    "name": "modx_list_user_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
usergroupYesUser group id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and does not meet it. It says nothing about pagination (despite limit/start parameters), what fields a member record contains, ordering, or access requirements.

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?

A single front-loaded sentence with no wasted words, which is structurally fine. However, the brevity here reflects under-specification rather than discipline, since a three-parameter tool needs far more than one clause.

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

Completeness2/5

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

With three parameters, no annotations, and no output schema, the description should explain paging behavior and the shape of returned members. It does neither, leaving the agent to guess at result boundaries and member representation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: the 'usergroup' id is documented in the schema, but 'limit' and 'start' are completely undocumented in both schema and description. The description never mentions paging, so an agent gets no meaning for those two parameters anywhere.

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 names a specific verb ('List') and resource ('members of a user group'), which is enough to distinguish it from modx_get_user_group (single group record) and modx_list_user_groups (groups themselves). It stops short of explicitly contrasting those siblings, but the operation 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 Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites such as needing a valid group id or elevated permissions, and no pointer to alternatives like modx_get_user_group or modx_add_user_to_group. The agent must infer everything from the 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