Skip to main content
Glama
Sign In
IMALI Commander

IMALI Commander

Official
by IMALI-DEFI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_files

Lists files in an approved workspace directory, helping AI assistants inspect available content before reading, writing, or searching.

Instructions

List files within approved workspace

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": "list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryNo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.6/5.0
Behavior2/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 not say whether listing is recursive, whether it includes hidden files or directories, how large results are paged, or what 'approved workspace' restricts; the only disclosed behavior is the workspace boundary.

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 the scope constraint front-loaded and zero filler. It is concise but borders on under-specification, leaving no room for the details an agent needs.

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?

The tool is simple (one optional parameter, no output schema), but with no annotations and no return-format information the definition leaves open what a listing returns and how deep it goes. Given that safety and structure data are absent, the description should do noticeably more.

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% for the single 'directory' parameter, which has a default of '.'. The description adds nothing about its format (relative vs absolute, subdirectory semantics) or whether omission means the workspace root, so it fails to compensate for the coverage gap.

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 ('List files') plus a scope qualifier ('within approved workspace'), which lets an agent separate it from write-oriented siblings like write_file or upload_file. Differentiation from search_files is not made explicit, and 'approved workspace' is never defined.

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 when-to-use guidance, no statement of when not to use it, and no reference to alternatives such as search_files for filtered listing. The agent must infer the choice entirely from the name.

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