Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_contexts

List MODX contexts with key, name, description, and rank, using query, start, and limit to browse available site contexts.

Instructions

List contexts (modContext): key, name, description, rank.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
startNo

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 and largely drops it. It does not state whether results are paginated, whether query does substring or exact matching, whether all contexts are visible or only those the user has access to, or ordering behavior.

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, front-loaded with the verb and resource, with no filler. Its brevity is not wasteful phrasing, though the space saved is not reinvested in the missing parameter and pagination detail.

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 list tool with no annotations and no output schema, the description conveys only the returned field names. Given three undocumented parameters and a large sibling surface of context-related tools, it leaves the agent without enough to call it confidently or correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters (limit, query, start) have 0% schema description coverage, and the description mentions none of them — it only enumerates returned fields. The agent gets no signal about what query matches against or how start/limit interact.

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 gives a specific verb and resource ("List contexts") and names the underlying object type (modContext) plus the fields returned (key, name, description, rank). An agent can tell it retrieves a collection rather than a single item, though it does not explicitly distinguish itself from modx_get_context or modx_list_context_settings.

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_get_context (single context) or modx_list_context_settings (settings within a context). The agent must infer the distinction from tool names alone.

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