Skip to main content
Glama
Sign In
IMALI Commander

IMALI Commander

Official
by IMALI-DEFI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_directory

Create a directory inside an approved workspace to organize files and keep file operations within a scoped, permitted location.

Instructions

Create a directory within approved workspace

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": {
      "directory": "<directory>"
    },
    "name": "create_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.7/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 disclosure burden, and it discloses almost nothing. It does not say whether creation is recursive, what happens if the directory already exists, what permissions or approval are required, or whether the effect is reversible.

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?

The definition is a single front-loaded phrase with zero filler, which is structurally sound. Its brevity is under-specification rather than verbosity, so it is not penalized here beyond losing the top score.

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?

This is a mutating filesystem tool with no annotations, no output schema, and an undocumented parameter. Given those gaps, the description should at minimum cover path semantics, collision behavior, and the 'approved workspace' restriction, none of which are present.

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?

The single parameter has 0% schema description coverage, so the description must compensate and does not. It never clarifies whether 'directory' is an absolute path, a workspace-relative path, a name, or a nested path, nor what characters or depth are permitted.

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?

The description uses a specific verb plus resource ('Create a directory') and adds a scope qualifier ('within approved workspace'), so the agent knows exactly what operation it triggers. It does not explicitly distinguish itself from write_file or upload_file, which is the only thing keeping it from a 5.

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 statement of when to use this versus the file-writing siblings, nor any precondition such as whether the parent must exist or whether the target must be empty. The phrase 'approved workspace' hints at a boundary but is never explained as a usable constraint.

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