Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

File Info Tool

aimage.file_info

Returns file size, pixel dimensions, and public URL for an image path relative to the file-manager root, so you can verify an asset before using it in Evolution CMS content.

Instructions

Details (size, dimensions, public URL) of one image the acting manager may see.

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": {
      "path": "<path>"
    },
    "name": "aimage.file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath relative to the file-manager root, as returned by aimage.files

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?

With no annotations, the description carries the full burden; it does disclose a meaningful behavioral trait -- access is limited to images 'the acting manager may see', implying permission-scoped visibility. It does not state that the operation is read-only, what happens for an unknown or unauthorized path, or whether the URL is temporary, which leaves real behavioral gaps for a no-annotation tool.

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 front-loaded sentence with no wasted words, and the returned-field parenthetical is efficient. Slightly awkward phrasing ('the acting manager may see') costs a point but nothing is padded.

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 one-parameter read tool with no output schema, describing the return contents (size, dimensions, public URL) fills the main gap. Remaining omissions -- URL lifetime, error behavior on bad/invisible paths -- are modest but non-trivial for a permission-scoped lookup.

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?

Only one parameter and schema coverage is 100%, so the schema already explains 'path relative to the file-manager root, as returned by aimage.files'. The description adds no further syntax, format, or constraint detail beyond that, so baseline 3 applies.

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?

Specific verb implied (retrieve) plus a single resource (one image's details), and it names the returned fields: size, dimensions, public URL. An agent can tell this apart from aimage.files, which lists files, because of the explicit 'one image' scoping. It falls short of a 5 only because it never names the sibling it differs from.

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: 'one image' signals single-item lookup, and the schema's path description points back to aimage.files as the source of the path. There is no explicit when-to-use/when-not guidance and no named alternative in the description itself.

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