Skip to main content
Glama

Coline

Create a folder

create_folder

Creates a folder in a drive, at its top level or inside another folder.

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": {
      "workspace": "<workspace>",
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
driveIdNoDefault: the person's default drive.
parentIdNoFolder id from list_drive_files.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
typeYes
fileIdYes
folderYes
updatedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered by structured data and the description does not contradict it. Beyond that the description adds no behavioral context: nothing about duplicate-name handling, permission requirements, or what happens to existing folders. The lower bar for annotated tools makes this adequate but thin.

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 no filler. Slightly redundant in restating 'in a drive' when driveId already defaults, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and most parameters are documented in the schema. What is missing for a mutation tool is behavioral context an agent would want before calling: uniqueness rules, required permissions, and effect when parentId is omitted.

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 coverage is 75% and the schema itself explains driveId's default, parentId's source (list_drive_files), and the workspace slug format. The description adds only the top-level-vs-nested framing, which the parentId description already implies, so it neither compensates nor detracts.

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?

Clear verb+resource: 'Creates a folder in a drive'. The phrase 'at its top level or inside another folder' scopes the operation precisely. It does not name a sibling to differentiate from (e.g. create_shared_drive), but the resource 'folder' is specific enough to separate it from the other create_* tools.

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 when-to-use / when-not-to-use guidance, no prerequisites, no named alternatives. The only usage-adjacent signal is the top-level vs nested choice, which is really about parameter interpretation rather than tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources