Skip to main content
Glama

Create a folder

create_folder

Use this when the user wants a new folder to group lists in, for people lists (the default) or for company lists. No two folders for one kind of list share a name. Free. It moves no list: a list is put in a folder by changing the list.

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
nameYesThe folder's name. No two folders for one kind of list share a name.
typeNoThe kind of list the folder holds: people (the default) or company.people

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the bar is lower; the description still adds real behavior: per-kind name uniqueness (a failed-create risk) and 'Free', a cost signal an agent can use to act without confirmation. It does not state what is returned or whether the creator needs particular permissions, and the non-idempotent hint is never explained.

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?

About forty words in four front-loaded sentences with no filler; the trigger condition leads. The clipped 'Free.' fragment and the colon-joined 'It moves no list' clause are terse but each carries information an agent needs.

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 two-parameter create tool with full schema coverage and no output schema, the description covers trigger, scope, uniqueness constraint, cost, and the notable absence of list side effects. Only the response shape and permission requirements are left unstated, which is a minor gap at this complexity.

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 100%, and the description's mentions of the name uniqueness rule and the people/company type with people as default mostly restate the schema fields. Baseline 3 applies since the schema already does the heavy lifting, with no added format or example guidance beyond the schema's own.

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?

Specific verb and resource (create a folder) plus the grouping purpose and the two allowed kinds (people, default; company). It also distinguishes itself from list operations by stating 'It moves no list: a list is put in a folder by changing the list', which separates it from create_list and any add-to-folder behavior, though it never names the sibling that does the moving.

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?

Opens with an explicit trigger ('Use this when the user wants a new folder to group lists in') and carves out a clear non-use case by pointing out that folder assignment happens via changing the list, not here. It stops short of naming the alternative tool that performs that assignment.

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