Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_resourcegroup_access

List resource-group access ACL entries, optionally filtered by user group, to audit which MODX user groups can access resources.

Instructions

List resource-group access ACL entries.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
startNo
usergroupNo

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, and it discloses almost nothing beyond read semantics implied by 'List'. It does not mention pagination defaults, sort order, whether all groups are returned or only those with ACL entries, or what fields an 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 crosses into under-specification rather than disciplined conciseness.

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 three undocumented parameters, the definition leaves the agent without enough context to call the tool confidently or interpret its results. A list tool in an ACL domain should at minimum state filtering and pagination 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?

Schema description coverage is 0% across three parameters (limit, start, usergroup), and the description adds no meaning for any of them. In particular the 'usergroup' filter — the one parameter that materially changes results — is never explained, so an agent must guess whether it narrows by user group ID or resource group.

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 names a specific verb and resource ('List resource-group access ACL entries'), so the agent knows exactly what is retrieved. It does not distinguish this read tool from sibling mutation tools such as modx_grant_resourcegroup_access, modx_revoke_resourcegroup_access, or modx_update_resourcegroup_access, leaving that differentiation to the name alone.

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 call this versus the grant/revoke/update siblings, nor any stated prerequisites such as needing an existing resource group or sufficient permissions. The only implied usage comes from the verb 'List'.

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