Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Files Tool

aimage.files

Lists images and folders visible to the acting manager under the file-manager root, with optional recursive scanning of subfolders.

Instructions

List images and folders the acting manager may see, under their file-manager root.

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": "aimage.files"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoFolder relative to the images root (default: the images root)
recursiveNoInclude subfolders

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals the authorization behavior (results are filtered to what the acting manager may see) and that listing is anchored at a file-manager root, but says nothing about ordering, pagination, result caps, or whether folder entries are distinguished from image entries in the output.

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 well-formed sentence with the scope and permission constraint front-loaded and no filler. It is efficiently sized, though its brevity comes at the cost of the behavioral and result-shape detail an agent would need.

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

Completeness4/5

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

For a two-parameter, zero-required read tool this covers the essentials: what is listed, under what permission model, and from which root. The absence of an output schema means the description could have said more about the shape of returned entries, but nothing critical to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (folder, recursive) are already documented, establishing a baseline of 3. The description adds no syntax, path-format, or default behavior beyond what the schema states, and it introduces a minor vocabulary mismatch by calling the anchor a "file-manager root" while the schema calls it the "images root".

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 ("List") and concrete resources ("images and folders"), plus a permission scope ("the acting manager may see") and a location constraint ("under their file-manager root"). This is enough to separate it from a detail-oriented sibling like aimage.file_info, though it never explicitly contrasts itself with browse-style siblings such as amount.browse.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the entry point for enumerating the file tree, and the mention of what the acting manager "may see" hints at permission-based scoping. There is no explicit when-to-use statement, no stated exclusion, and no named alternative for drilling into a single file or for keyword search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.