Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_get_media_source

Retrieve a single MODX media source by ID or name to inspect media storage configuration for safe resource and template management.

Instructions

Get one MODX media source.

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

Input Schema

NameRequiredDescriptionDefault
idNo
nameNo

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 exist, so the description carries the full disclosure burden, yet it says nothing about what happens if neither id nor name is supplied, whether both can be combined, what precedence applies, or what an error looks like. Only the implicit read-only nature of "Get" is conveyed.

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

Conciseness3/5

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

A single short sentence with no wasted words and a front-loaded verb, which is good structure. However, the brevity reflects under-specification rather than disciplined concision, so it earns only a middling score.

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 tool with zero annotations, zero schema coverage on two ambiguous optional parameters, and no output schema, the description is far too thin to let an agent call it confidently. It should at minimum cover identifier precedence and the return shape.

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% and both parameters are optional, so the description must explain id vs name lookup and precedence—it does neither. The word "one" hints that the parameters act as identifiers, but nothing distinguishes id-based from name-based selection.

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?

States a specific verb ("Get") and resource ("media source") with a singular scope ("one"), which implicitly contrasts with the sibling modx_list_media_sources. It never names or explicitly distinguishes itself from siblings like modx_update_media_source or modx_get_system_setting, so it stops short of 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 tool rather than modx_list_media_sources or modx_get_media_source-ish alternatives, and no prerequisites or conditions are given. An agent must infer that this is for fetching a single record by looking at the name 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