Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_run_processor

Executes any MODX processor directly as an escape hatch, so AI agents can call processors without a dedicated tool. Requires the allow_run_processor setting to be enabled.

Instructions

Run ANY MODX processor directly (escape hatch). Requires the modxmcp.allow_run_processor setting to be enabled. High privilege — prefer a dedicated tool when one exists.

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": {
      "processor": "<processor>"
    },
    "name": "modx_run_processor"
  }
}

Input Schema

NameRequiredDescriptionDefault
processorYesProcessor path, e.g. 'security/user/getlist' (relative to processors_path).
propertiesNoProcessor properties/params.
processors_pathNoOverride processors base path (for component processors).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the privilege level ('High privilege') and the config gate that must be enabled, which are genuinely useful. It does not disclose that arbitrary processors may mutate or delete data, how failures surface, or what the response shape is, so behavioral coverage is partial.

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

Conciseness5/5

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

Three short sentences, each carrying a distinct load: capability, precondition, and privilege/routing warning. The escape-hatch framing is front-loaded and there is zero filler.

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

Completeness3/5

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

For a generic escape hatch with no output schema and no annotations, the definition covers capability, gate, and privilege but leaves return values and error behavior undefined — an agent cannot anticipate what comes back from an arbitrary processor. Adequate to invoke correctly, incomplete for interpreting results.

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

Parameters3/5

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

Schema description coverage is 100%, so processor, properties, and processors_path are already documented in the schema, and the description adds nothing beyond them. The description does not clarify the nested 'properties' object's expected keys or how processors_path selects component processors, so baseline 3 applies.

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?

States a specific verb and resource ('Run ANY MODX processor directly') and frames the scope with '(escape hatch)', so an agent can tell it apart from the many dedicated modx_* tools. It stops short of explaining what a processor invocation returns, but the action itself 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 Guidelines4/5

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

Gives an explicit routing rule — 'prefer a dedicated tool when one exists' — plus a hard prerequisite ('Requires the modxmcp.allow_run_processor setting to be enabled'). It does not say how to discover which processors exist or when no dedicated tool applies, so guidance is strong but not exhaustive.

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