Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_create_user_group

Creates a MODX user group with a required name and optional parent group ID to organize users within the correct hierarchy.

Instructions

Create 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": {
      "name": "<name>"
    },
    "name": "modx_create_user_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
parentNoParent user group id (0 = none).

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?

With no annotations, the description carries the full burden of behavioral disclosure for a write operation. It does not state required permissions, whether the group name must be unique, what happens with an invalid parent id, or what the call returns — only that a creation occurs.

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 single short sentence is front-loaded and free of waste, but it is terse to the point of under-specification rather than deliberate conciseness. It does not earn much credit as structure because there is hardly any content to structure.

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?

For a mutation tool with no annotations and no output schema, the definition should cover permissions, uniqueness constraints, and the meaning of the parent parameter. It covers none of these, leaving the agent without enough context to call the tool confidently.

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 50%: the 'name' parameter has no schema description, and the description adds no meaning for either 'name' or 'parent'. The only parameter detail ('0 = none' for parent) lives in the schema, so the description does not compensate for the coverage gap.

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 ("Create") and resource ("user group"), which is enough to distinguish it from the sibling list/update/delete user-group tools. It stops short of any scope detail (e.g., what a group entails), but the core action 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 guidance on when to use this instead of modx_list_user_groups, modx_update_user_group, or modx_create_role, and no prerequisites or exclusions are mentioned. The verb 'create' implies usage, but the agent gets no explicit context.

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