Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_update_context

Updates a MODX context's name, description, or rank and can apply advanced context settings via a JSON array.

Instructions

Update a context (name/description/rank). 'settings' may be a JSON array of context settings (advanced).

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

Input Schema

NameRequiredDescriptionDefault
keyYes
nameNo
rankNo
settingsNo
descriptionNo

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 provided, so the description carries the full behavioral burden for a mutation tool. It never states what permissions are needed, whether omitted fields are preserved or cleared, whether 'settings' overwrites all existing context settings or merges, or what is returned.

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?

Two tight sentences with the primary action front-loaded and no filler. It is appropriately sized but slightly too terse for the tool's complexity.

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?

A five-parameter mutation tool with no annotations, no output schema and 0% schema coverage needs far more: the role of 'key', the merge/replace semantics of 'settings', and failure or permission behavior are all missing. The description leaves key questions unanswered for an agent to call it safely.

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 five parameters. The description covers name/description/rank by implication and clarifies that 'settings' is a JSON array of context settings, but the required 'key' parameter (the context identifier) is never explained, nor are the element format of the settings array or valid rank values.

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?

Names a specific verb and resource ('Update a context') and enumerates the updatable fields (name/description/rank), which clearly separates it from modx_get_context and modx_list_contexts. It stops short of explicitly contrasting with modx_create_context or modx_delete_context, so a 4 rather than a 5.

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_update_context_setting, modx_create_context, or other sibling mutations, and no stated prerequisites. The only usage hint is the parenthetical '(advanced)' on the settings parameter.

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