Skip to main content
Glama
TripQi

Code Editor MCP Server

by TripQi

dir_ops

Manage directories by creating, listing, or deleting them. Supports tree or flat listing with depth control, ignore patterns, and safe deletion with conflict detection.

Instructions

Directory operations: create, list, or delete.

Args: action: "create" | "list" | "delete" dir_path: Absolute path to the directory. depth: Listing depth (list only). format: "tree" | "flat" (list only). ignore_patterns: Glob patterns to exclude (list only). max_items: Max entries for flat listing. expected_mtime: Required for delete (conflict detection). confirm_token: Required for delete ("delete:<normalized_path>"). allow_nonempty: Required for delete (explicit bool).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
dir_pathYes
depthNo
formatNotree
ignore_patternsNo
max_itemsNo
expected_mtimeNo
confirm_tokenNo
allow_nonemptyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description must disclose behaviors. It mentions safety requirements for delete (expected_mtime, confirm_token, allow_nonempty) but lacks details on success/failure returns, side effects, or output format.

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?

Structured as a Python docstring with clear Args: section. Every line is informative, no redundant text. Concise and well-organized.

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?

Covers basic semantics for all parameters and actions, sufficient for correct invocation. Lacks overall context about output schema (though present), error handling, or interaction with sibling tools.

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

Parameters5/5

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

Schema has 0% description coverage; description adds meaning for all 9 parameters via the Args section, including constraints like 'list only' for depth, format, etc. Fully compensates for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Directory operations: create, list, or delete', clearly indicating the tool's scope and actions. It distinguishes from sister tool 'file_ops' by specifying directory-specific operations.

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?

No explicit guidance on when to use this tool versus alternatives like 'file_ops' or 'edit_block'. The description only lists parameters without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TripQi/code-editor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server