Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_get_context_setting

Retrieves a single MODX context setting by context key and setting key, helping you look up configuration values for a specific context.

Instructions

Get one context setting (by context_key + key).

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>",
      "key": "<key>"
    },
    "name": "modx_get_context_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
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?

No annotations are supplied, so the description carries the full behavioral burden. It implies a read but says nothing about what happens when the setting is absent — whether an error is returned or a system-level default is resolved — which is the key behavioral question for MODX context settings that override system settings.

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?

One short sentence with the identifying detail front-loaded and no filler. It is terse rather than padded, though it errs toward under-specification rather than wasted words.

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 two-required-parameter tool with no annotations, no output schema, and zero schema coverage, the description should at least describe the return shape or not-found behavior. As written, an agent must discover both parameter formats and failure semantics by trial.

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 both parameters are undocumented in structured form. The description names them (context_key + key) but adds no meaning: no format, no example values, no note on case sensitivity or whether context_key defaults to the current context.

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 states a specific verb and resource, "Get one context setting," and the qualifier "one" distinguishes it from the sibling modx_list_context_settings. It does not explicitly contrast with modx_get_system_setting or modx_get_settings variants, but the resource noun is specific enough for an agent to select it.

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_context_settings (to enumerate) or modx_get_system_setting (for global defaults). Usage is only implied by the tool name and the parenthetical parameter hint.

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