Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_update_resource_tvs

Updates template-variable values for a specific MODX resource by ID, enabling targeted content changes without rewriting the entire resource.

Instructions

Update a resource's template-variable (TV) values.

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": {
      "resource_id": "<resource_id>",
      "tvs": "<tvs>"
    },
    "name": "modx_update_resource_tvs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tvsYes
resource_idYes
_runtime_preconditionsNoInternal Site Agent CAS preconditions; never author manually.

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 burden of behavioral disclosure and adds almost nothing: it does not say whether the 'tvs' object replaces all existing TV values or merges partially, whether omitted TVs are cleared, or what permissions/context are required. For a destructive-capable write operation this is a significant gap.

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 short sentence with no filler and the core action front-loaded. Its brevity is efficient, though it borders on under-specification rather than padding.

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 mutation tool with a nested-object parameter, no annotations, and no output schema, the definition omits replace-vs-merge semantics, key format for 'tvs', and any error/return behavior. An agent could easily call it incorrectly and silently wipe TV values.

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 only 33%, and the most important parameter, 'tvs', is an untyped-key object with no description of its shape (TV name to value mapping, types, null handling). The description adds no parameter meaning at all, so it fails to compensate for the low coverage.

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 names a specific verb (update) and resource (a resource's template-variable values), so an agent knows it is a mutation of TV values on a single resource. It does not explicitly contrast itself with close siblings like modx_get_resource_tvs, modx_list_tv_values, or modx_clear_tv_values, leaving differentiation to the name alone.

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 statement of when to use this tool versus modx_list_tv_values (read) or modx_clear_tv_values (clear), nor any prerequisite such as needing an existing resource. Usage is only inferable from the verb 'update', which is weak guidance for a mutation in a family of TV tools.

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