Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_virtualpage_create_handler

Create a VirtualPage handler to map requests to resources, snippets, chunks, templates, or dynamic resources with rank, cache, and active settings.

Instructions

Create a VirtualPage handler. type can be resource, snippet, chunk, dynamic_resource/template, or 0..3.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
rankNo
typeNo
cacheNo
entryNo
activeNo
contentNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.7/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 behavioral burden, but “Create” merely signals a write operation. It says nothing about persistence, duplicate names, defaults, activation/cache effects, validation, permissions, or failure behavior.

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

Conciseness4/5

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

The description is short and front-loads the operation, with no filler. Its compressed “dynamic_resource/template” and “0..3” notation sacrifices some clarity, but the overall structure is efficient.

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?

The schema supports a minimal name-only invocation, but the definition is insufficient for confidently configuring an eight-parameter create operation with no annotations or output schema. It omits handler purpose, parameter defaults and semantics, side effects, and expected creation 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?

Only type is discussed, and its listed values largely repeat the schema enum without mapping numeric codes 0–3 to their meanings. With 0% schema description coverage, name, rank, cache, entry, active, content, and description remain unexplained, while “dynamic_resource/template” is ambiguous shorthand.

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 VirtualPage handler” gives a specific verb and resource, and the create action distinguishes it from the get/update handler siblings. However, it never explains what a handler does or its functional relationship to VirtualPage routes and events.

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?

Usage is only implied: use this to create rather than update a handler. There is no guidance about prerequisites, when a handler is needed, or when to use create_route or create_event instead.

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