Skip to main content
Glama
Sign In
IMALI Commander

IMALI Commander

Official
by IMALI-DEFI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

download_file

Read a workspace file up to 5 MB and return its contents as base64 for transfer to an MCP client.

Instructions

Read a small workspace file as base64 for transfer to an MCP client (max 5 MB)

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": {
      "file": "<file>"
    },
    "name": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/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 behavioral burden. It does disclose two useful traits: output is base64-encoded and there is a hard 5 MB maximum, but it never says what happens when a file exceeds the cap (error vs. truncation), whether the read is non-destructive, or what permissions are required.

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

Conciseness5/5

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

A single front-loaded sentence with the purpose, encoding, consumer, and size limit — no filler or redundancy. Every clause earns its place.

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?

There is no output schema, and the description does cover the return form (base64) and the size ceiling, which is what an agent most needs. The remaining gap is failure behavior above 5 MB, which is minor for a simple one-parameter read tool.

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?

With one parameter at 0% schema description coverage, the description must compensate and only partly does: 'workspace file' implies the path is workspace-relative rather than an absolute host path. It adds no detail on path format, escaping, or whether directories are valid inputs.

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 and resource ('Read a small workspace file as base64') plus the intended consumer ('for transfer to an MCP client'), which distinguishes it from a plain file read. It does not name read_file or otherwise explicitly separate itself from the closest sibling, keeping it at 4 rather than 5.

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?

The 'for transfer to an MCP client' phrase and the 5 MB ceiling imply when this tool is appropriate, and the size cap hints that larger files belong elsewhere. However, there is no explicit when-not guidance or named alternative such as read_file or a chunked transfer path, so usage must be inferred.

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