Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_users

Lists MODX manager and web users with optional query, start, and limit parameters so you can retrieve and review user accounts.

Instructions

List manager/web users (modUser).

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": "modx_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it says nothing about pagination defaults, result ordering, filtering behavior for 'query', or whether inactive/disabled users are included. Only the parenthetical '(modUser)' hints at the data model.

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

Conciseness2/5

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

The single sentence is front-loaded and free of waste, but at this length it is under-specified rather than concise, leaving key facts about a three-parameter listing tool unstated.

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?

Three undocumented parameters, no annotations, and no output schema mean the description would need to do real work to make the tool callable correctly, and it does almost none. An agent cannot predict result shape, pagination contract, or filter behavior.

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 description coverage is 0% and the description never mentions limit, query, or start. The names are conventional enough that an agent can guess at pagination and search, but the definition adds no meaning about match semantics for 'query' or whether 'start' is offset in rows.

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?

The description states a specific verb and resource ('List ... users') and clarifies the underlying object type as modUser, distinguishing it from modx_get_user by plurality. However, it never names a sibling or explains the 'manager/web' distinction in actionable terms, so the agent must infer scope from the name 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?

There is no when-to-use guidance, no indication of when to prefer modx_get_user for a single user versus this list operation, and no mention of required permissions. The agent gets no routing signal beyond the verb 'List'.

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