Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_resource_group_resources

Retrieve all resources assigned to a specific resource group to audit membership and manage group-based access in MODX.

Instructions

List resources assigned to a resource group.

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": {
      "resourceGroup": "<resourceGroup>"
    },
    "name": "modx_list_resource_group_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceGroupYes

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies read-only behavior through the verb 'list'. It says nothing about permission/authority requirements for reading group membership, whether results are paginated or truncated, or what fields each resource entry contains.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the gaps noted in other dimensions.

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 read tool with no annotations and no output schema, the description should at least pin down the parameter's identifier type and give a sense of the returned shape. Neither is present, leaving the agent to guess how to construct a valid 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%, so the single 'resourceGroup' parameter is undocumented structurally. The description hints it is a group reference but does not clarify whether it is a numeric ID, a name, or a code, which is the one detail an agent most needs for a 1-param tool.

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 gives a specific verb ('List') and a precise resource ('resources assigned to a resource group'), which clearly distinguishes it from modx_list_resource_groups (groups themselves) and modx_list_resources (all resources). It stops short of naming those siblings explicitly, so the differentiation has to be inferred from the phrasing.

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 guidance on when to use this versus modx_list_resources, modx_get_resource_group, or modx_list_resourcegroup_access, nor any stated prerequisite such as needing a valid group ID or sufficient permissions. The agent must guess the selection context.

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