Skip to main content
Glama
Hackeatutiempo

Mapache

by Hackeatutiempo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Create a folder

create_folder

Create a sidebar folder to organize boards, optionally nested under an existing parent. Returns its ID; boards can auto-create folders from a path, so manual use is rare.

Instructions

Create a folder in the sidebar to organize boards, optionally inside another folder. Always creates a new folder, even if one with the same name exists; returns its id. You rarely need it: create_board and update_board create missing folders by themselves when you pass a folder path.

Input Schema

NameRequiredDescriptionDefault
iconNoAn emoji shown before the name
nameYesFolder name as shown in the sidebar
colorNoColor of the folder in the sidebar (default none)
parentNoParent folder name, path ("Work / Clients") or id; it must already exist (you get an error otherwise). Leave out for a top-level folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.3
    • addedInput schema / properties / color / description
      Added value: +"Color of the folder in the sidebar (default none)"
    • changedInput schema / properties / icon / description
      Previous value: -"An emoji"New value: +"An emoji shown before the name"
    • addedInput schema / properties / name / description
      Added value: +"Folder name as shown in the sidebar"
    • changedInput schema / properties / parent / description
      Previous value: -"Parent folder name, path or id"New value: +"Parent folder name, path (\"Work / Clients\") or id; it must already exist (you get an error otherwise). Leave out for a top-level folder"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so safety is covered. The description adds real behavioral value anyway: it confirms non-idempotency in plain language ('Always creates a new folder, even if one with the same name exists'), states that the returned id is the useful output, and warns that the parent must already exist or you get an error.

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?

Three tight sentences, front-loaded with the core action, then the non-idempotency caveat, then the routing guidance to siblings. No filler or restatement of the title.

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

Completeness5/5

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

There is no output schema, but the description closes that gap by saying it returns the folder id. Combined with the error condition on parent and the sibling routing, an agent has everything needed to call it correctly.

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%, so name, icon, color and parent are fully documented in the schema itself, making 3 the baseline. The description only gestures at placement ('optionally inside another folder') without adding syntax or format detail, so it does not exceed the schema's own documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 in the sidebar') plus the scope it affects (organize boards). It also positions itself against siblings by noting create_board/update_board handle folders implicitly, so an agent can disambiguate without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says 'You rarely need it' and names the alternatives (create_board, update_board) along with the condition under which they cover the need (passing a folder path). This is a rare case of an explicit when-not-to-use plus a named substitute.

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