Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_ms2_update_category

Updates a miniShop2 category by ID, allowing changes to its alias, parent, title, and published status.

Instructions

Update a miniShop2 category.

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": {
      "id": "<id>"
    },
    "name": "modx_ms2_update_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
aliasNo
parentNo
pagetitleNo
publishedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2/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 fails to meet it. It signals mutation only through the word "Update"; it does not say whether unspecified fields are preserved, whether alias uniqueness is enforced, what permissions are required, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but at this length that reflects under-specification rather than conciseness. For a five-parameter mutation tool the brief leaves no room for the guidance an agent actually needs.

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

Completeness1/5

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

Given a mutation tool with five undocumented parameters, no annotations and no output schema, the description conveys essentially nothing beyond the tool name. An agent could not confidently call this tool without trial and error.

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?

Schema description coverage is 0% across five parameters, and the description names none of them. id, alias, parent, pagetitle and published are left entirely unexplained, including the ambiguous numeric type for published.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("Update" + "miniShop2 category"), which tells an agent this mutates a shop category rather than a MODX resource. However, it is nearly a restatement of the tool name and never distinguishes it from siblings such as modx_ms2_create_category or modx_ms2_list_categories.

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 when-to-use guidance, no prerequisite or permission context, and no mention of alternatives. The agent must infer from the name alone that this is the tool for modifying an existing category rather than creating one.

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