Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_resource_groups

Retrieve MODX resource groups with their IDs and names, using optional query, start, and limit parameters to find and paginate groups for access control or content organization.

Instructions

List resource groups (id, name).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modx_list_resource_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.6/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 adds almost nothing: it does not say the operation is read-only, whether results are paginated, how many records are returned by default, or whether it needs an admin permission. Only the returned field list hints at the response shape.

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?

One short, front-loaded sentence with no filler, which is structurally good. However, the terseness reads as under-specification rather than economy, since the single clause leaves the tool's filtering and paging behavior unexplained.

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?

With no annotations, no output schema, and undocumented parameters, the description should explain return shape and pagination behavior, but it only lists two field names. For a searchable list endpoint this leaves an agent guessing at anything beyond the basic call.

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% for three parameters (limit, query, start), and the description never mentions them. An agent cannot tell what "query" searches on (name only? name and description?) or what units limit/start use, so the description fails to compensate for the schema gap.

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 uses a specific verb ("List") on a specific resource ("resource groups") and even names the returned fields (id, name), which makes it easy to separate from modx_get_resource_group and modx_create/update/delete_resource_group. It stops short of explicitly naming those siblings, so a 4 rather than a 5.

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 statement of when to use this tool versus modx_get_resource_group, modx_list_resource_group_resources, or modx_list_resourcegroup_access. The agent must infer usage purely from the name; no prerequisites, exclusions, or alternatives are offered.

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