Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_create_role

Create a MODX user role by defining its name and authority level, enabling permission assignment for users.

Instructions

Create a role.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
authorityNoAuthority level (lower = more authority).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses nothing: not whether the call fails on a duplicate role name, not what authority defaults to when omitted, not whether the new role is immediately usable in access policies, and not what the response contains.

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?

Three words with zero waste and the verb-resource pair front-loaded, but this is under-specification rather than disciplined concision; the sentence is too thin to earn its place as the tool's only guidance.

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, no output schema, and a partially documented schema, the description should at least cover authority semantics and side effects. It covers none of that, leaving the agent to infer everything from the parameter names.

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 50%: the schema itself explains the authority ordering, while name is undocumented but self-evident as a required string. The description adds no meaning to either parameter, so it fails to compensate for the gap and merely restates the operation.

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?

"Create a role" names a specific verb (create) and resource (role), which is enough for an agent to understand the operation itself. It offers no differentiation from the obvious siblings modx_update_role, modx_delete_role, or modx_list_roles, and never says what a role is in this system.

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 at all: nothing says to use this instead of modx_update_role when a role already exists, nothing about required permissions, and nothing about prerequisites such as access policies needing to exist first.

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