Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_context_settings

Lists settings for a MODX context by context key, with optional area, namespace, and pagination filters, so you can inspect configuration values without editing them.

Instructions

List settings of a context (modContextSetting).

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": {
      "context_key": "<context_key>"
    },
    "name": "modx_list_context_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
limitNo
startNo
namespaceNo
context_keyYes

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?

With no annotations at all, the description carries the full disclosure burden and offers only the word 'List', which weakly implies read-only. It says nothing about pagination despite limit/start parameters, nothing about permissions or context access requirements, and nothing about whether unset/inherited settings are included.

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 short sentence with the resource front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than tight editing.

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 five-parameter list tool with no annotations, zero schema descriptions, and no output schema, one sentence is not enough. An agent gets no guidance on filtering by area/namespace, on paginating via limit/start, or on what a returned setting record contains.

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% and the description only accounts for context_key via the phrase 'of a context'. The purpose of area, namespace, limit, and start — the filtering axes most likely to matter here — is left entirely unexplained in both places.

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 pairs the verb 'List' with a specific resource, 'settings of a context', and even names the underlying MODX object (modContextSetting), which disambiguates it from the singular modx_get_context_setting and from modx_list_system_settings. It does not explicitly name those siblings as alternatives, which keeps it out of 5 territory.

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_context_setting, modx_list_system_settings, or modx_list_contexts. An agent must infer from the name alone that this is the bulk read for a single context's settings.

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