Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_system_settings

List MODX system settings, optionally filtered by area or namespace, to inspect configuration values and support auditing or troubleshooting.

Instructions

List MODX system settings.

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

Input Schema

NameRequiredDescriptionDefault
areaNo
namespaceNo

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, but it only implies a non-mutating read via the verb "List." It says nothing about permissions required, pagination, result volume, or whether all settings or only overridden ones are returned.

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?

The single short sentence is front-loaded and free of waste, but it is terse to the point of under-specification rather than tightly informative. There is no structure beyond the bare statement of purpose.

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 needs to explain return shape and filter semantics and does neither. For a listing tool with two filtering parameters this leaves the agent guessing at call correctness.

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% with two parameters, area and namespace, and the description never mentions either one. An agent cannot tell from the text whether these are exact-match filters, prefix filters, or required scoping values, so the coverage gap is not compensated.

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?

"List MODX system settings" gives a specific verb and resource, so an agent knows this is a read/lookup tool for the system settings table. It does not distinguish itself from nearby siblings such as modx_get_system_setting or modx_list_context_settings, which would matter for selection.

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 listing versus modx_get_system_setting for a single key, nor on when the area/namespace filters apply. The agent is left to infer usage entirely from the name.

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