Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_versionx_list_versions

List VersionX versions for MODX resources, chunks, snippets, templates, plugins, or TVs by type and ID to inspect revision history.

Instructions

List VersionX versions for a MODX resource, chunk, snippet, template, plugin, or TV.

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": {
      "type": "<type>",
      "content_id": "<content_id>"
    },
    "name": "modx_versionx_list_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
limitNo
content_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

B3/5.0
Behavior2/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 does not meet it. It never states that this is a read-only operation, whether the caller needs VersionX/permissions, what ordering the versions come back in, or what the response looks like. The only implicit signal is the verb 'List'.

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?

A single front-loaded sentence with zero filler; the verb and resource lead, and the type enumeration is the only elaboration. Nothing in it is redundant.

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 3-parameter tool with no annotations, no output schema, and 0% schema coverage, the description is too thin. An agent cannot learn from it what 'limit' does, what 'content_id' refers to, or what a returned version record contains, so it is not complete enough 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 description coverage is 0%, so the description must compensate and largely does not. The enumerated content types merely restate the existing 'type' enum, and neither 'content_id' (the ID of the element whose versions are wanted) nor 'limit' (maximum number of versions to return) is explained anywhere.

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 (List) and resource (VersionX versions) and enumerates the concrete content types it operates on, so an agent knows exactly what the tool returns. It stops short of naming the sibling tools it complements (modx_versionx_get_version, modx_versionx_revert_version), so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the verb 'List' – the natural reading is 'use this when you need version history for an element.' There is no explicit statement of when to prefer this over modx_versionx_get_version for a single version, and no prerequisites or exclusions are given.

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