Skip to main content
Glama

create_folder

Creates a Notes folder at the top level or inside a specified parent folder, optionally under a chosen account, and rejects duplicate folder names in the same location.

Instructions

Create a Notes folder. Give 'parent' to make it inside another folder. Without 'parent', it goes to the top level of 'account' (default: the default account). A folder with the same name in the same place is refused.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new folder, on one line.
parentNoParent folder name (any case) or id.
accountNoAccount name, for example iCloud. Ignores case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-open-world write, so the baseline bar is lower. The description still adds genuinely useful behavior beyond them: the duplicate-name-in-same-place refusal and the account defaulting rule, both of which affect whether a call succeeds. It omits what a successful call returns and what happens with a nonexistent parent.

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?

Four short sentences, front-loaded with the action, then the two optional-parameter behaviors, then the failure condition. No filler and nothing repeated from the schema or annotations.

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?

A low-risk 3-parameter mutation with full schema coverage needs mainly outcome and precondition detail. The description covers the duplicate-name failure and account defaulting, but leaves unstated whether the parent must already exist and what the response contains, which matters more given there is no output schema.

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?

With 100% schema description coverage the baseline is 3, and the schema already documents all three parameters including the case-insensitivity notes. The description contributes real meaning on top — nesting semantics of 'parent' and the default resolution for 'account' — but adds nothing about the required 'name' beyond what the schema states.

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?

Opens with a specific verb+resource pair ('Create a Notes folder'), which cleanly separates it from create_note, create_contact, and other create_* siblings by resource domain. It does not explicitly name list_folders or create_note as related tools, but the resource noun alone is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditional guidance: pass 'parent' to nest, omit it to land at the top level of 'account', and account itself defaults to the default account. It stops short of naming alternatives (e.g. list_folders to discover valid parents) or stating preconditions like the parent having to already exist.

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