Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_update_user_group

Update a MODX user group's name or parent to reorganize permissions and hierarchy. Use it to move groups under a new parent or rename them without recreating.

Instructions

Update 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": {
      "id": "<id>"
    },
    "name": "modx_update_user_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
parentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing: not whether updates require admin permissions, whether unspecified fields are preserved or cleared, whether the change is reversible, or what is returned. "Update" is the only hint about mutation semantics.

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?

It is a single short sentence, but that is under-specification rather than conciseness; the sentence conveys no information beyond the tool name and would need to grow substantially to be useful.

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

Completeness1/5

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

A destructive-by-nature mutation tool with zero annotation coverage, no output schema, and 0% parameter documentation is left almost entirely undefined. An agent cannot safely call it without guessing at field semantics and side effects.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description compensates for none of it. Nothing explains that id identifies the group to modify, that name renames it, or what parent does (nesting, or nullifying a hierarchy).

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

Purpose2/5

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

"Update a user group" merely restates the tool name modx_update_user_group; it adds no distinguishing scope. It does not say which aspects of a group are updatable (name, parent) or how this differs from sibling tools such as modx_create_user_group or modx_update_group_member.

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 prerequisites, and no pointer to alternatives. The agent cannot tell whether group membership changes belong here or in modx_update_group_member / modx_add_user_to_group.

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