Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

make_directory

Creates a folder at a relative path inside the workspace, letting you set up project directories before writing files or running commands.

Instructions

Create a folder inside the 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": "make_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesRelative folder path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-non-destructive profile is covered structurally. The description adds the useful detail that creation is confined to the workspace, which tells the agent paths cannot escape the sandbox. It omits idempotency and error behavior for pre-existing paths, which is the main gap for a mutation tool.

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?

One short sentence, front-loaded with the verb and containing no filler. Nothing in it is redundant given the annotations and schema.

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 single-parameter, no-output-schema tool this covers the essentials: what is created, where, and that it is a non-destructive write. The only missing piece an agent might want is behavior on an already-existing directory or nested paths, which is a minor gap at this complexity level.

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?

Schema description coverage is 100% and the single 'directory' parameter is documented as a 'Relative folder path'. The phrase 'inside the workspace' reinforces that the path is relative and sandboxed, but adds little beyond the schema. Baseline 3 applies when the schema already carries the parameter meaning.

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 ('Create a folder') plus a scope constraint ('inside the workspace'), so the operation is unambiguous at a glance. It does not distinguish itself from siblings such as move_path or delete_path, but the verb+resource combination is distinctive enough that confusion is unlikely.

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 by the verb – an agent knows to call it when a directory is needed, but there is no explicit guidance on when to prefer this over alternatives or on preconditions. No mention of whether the tool errors on an existing folder or creates missing parents.

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