Skip to main content
Glama
Sign In
forge

forge

by SoulNassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

workspace_create_folder

Creates a new folder in a project workspace to organize files, sections, or collections by specifying a relative path.

Instructions

Create a folder (a section or a collection).

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": {
      "path": "<path>"
    },
    "name": "workspace_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath relative to the workspace root.
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.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 behavioral burden, yet it says nothing about idempotency, what happens if the path already exists, required permissions, or whether creation is reversible. Only the bare fact that this is a mutating operation is conveyed.

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?

A single front-loaded sentence with the verb first and no filler. Its brevity is efficient, though it borders on under-specification rather than crispness.

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?

For a mutation tool with no annotations, no output schema, and one undocumented parameter, the description does far too little. It should at least cover the project parameter and error/existing-path behavior.

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 only 50%: 'path' is documented in the schema but 'project' is undocumented in both schema and description. The description does not compensate by explaining path format, allowed depth, or the role of the project parameter.

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 gives a specific verb+resource ("Create a folder") and adds a parenthetical hint about what a folder represents ("a section or a collection"). It is clear what the tool does, but it never distinguishes itself from siblings like workspace_write or workspace_move, which also mutate the workspace tree.

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 prerequisites, and no mention of alternatives. An agent reading this cannot tell whether a folder should be made with this tool or implicitly via workspace_write, nor what happens with nested paths.

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