Lists MODX media sources to identify configured storage locations for files and images before managing media.
List MODX media sources.
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_media_sources"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full disclosure burden. "List" weakly implies a read-only operation, but the description says nothing about whether pagination, filtering, or permissions apply, nor what the response shape looks like for a zero-parameter call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler or redundant restatement. It is appropriately terse for a no-argument list operation, though the terseness borders on under-specification rather than economy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and no parameter documentation, the description is the only source of behavioral detail — and it provides none beyond the name. An agent cannot tell what the returned records contain or whether results are scoped by context or permission.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero properties and full description coverage, so there are no parameter semantics to explain. Baseline of 4 applies per the zero-parameter rule; the description neither helps nor hurts here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ("List" + "MODX media sources"), which distinguishes it from get/create/update/delete siblings by the "list" verb alone. However, it adds nothing about what a media source is, what the listing contains, or how it differs from modx_get_media_source or modx_list_media_source_files beyond the verb.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of the sibling modx_list_media_source_files or modx_get_media_source as alternatives, and no prerequisites. The agent must infer the selection rule purely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.