Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_namespaces

List MODX namespaces with optional filtering and pagination to inspect names, paths, and asset paths for CMS setup and troubleshooting.

Instructions

List namespaces (modNamespace): name, path, assets_path.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It discloses the returned fields (name, path, assets_path), which is useful, but says nothing about pagination despite limit/start parameters, nothing about whether results are capped, and nothing about required permissions or read-only safety.

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 compact line with the verb and resource front-loaded and no wasted words. It is efficient, though the brevity borders on under-specification for a tool with three undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool this covers the core identity, and no output schema exists so return-value detail is reasonably sketched by the field list. However, the complete absence of pagination and filter semantics leaves real gaps for correct invocation.

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?

All three parameters (limit, query, start) have 0% schema description coverage, so the description is the only place semantics could be supplied — and it supplies none. In particular, it does not say whether "query" filters by namespace name, path, or something else, nor how limit/start 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 namespaces") and identifies the underlying MODX object (modNamespace) plus the fields returned. It is clearly distinguishable from the mutation siblings modx_create_namespace / modx_update_namespace / modx_delete_namespace, though it does not explicitly name them.

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 call this versus alternatives, no prerequisite or permission context, and no mention of how to page through results. The agent must 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