Skip to main content
Glama
Sign In
Kybase

Kybase

by Kyrzin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_folder

Create a new folder at the top level or nested under a parent folder to organize knowledge base content.

Instructions

Create a new folder. Optionally nested under a parent.

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
nameYesFolder name. Unique among its siblings — the same name under a different parent is fine
parent_idNoParent folder UUID. Omit or pass null to create it at the top level

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.1
    • addedInput schema / properties / name / description
      Added value: +"Folder name. Unique among its siblings — the same name under a different parent is fine"
    • changedInput schema / properties / parent_id / anyOf
      Previous value: -[
-  {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "uuid",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / parent_id / description
      Added value: +"Parent folder UUID. Omit or pass null to create it at the top level"
  2. First observedv1.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It states that a folder is created but does not disclose permissions, duplicate-name behavior, what the operation returns, or other side effects. The uniqueness constraint appears only in the schema, not in the description.

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?

The description is two short sentences with no wasted wording. The core purpose is front-loaded, and the optional nesting note follows immediately.

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?

The tool is simple and the schema fully documents both parameters, so an agent can invoke it correctly from the provided structured data. However, with no annotations and no output schema, the description could have said more about return values or error behavior for this mutation.

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 description coverage is 100%, so both parameters are already documented in detail, including the uniqueness rule and top-level behavior. The description adds only the high-level note that nesting is optional, which is already covered by the parent_id schema description.

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 states a specific verb and resource: "Create a new folder." It also clarifies the optional nesting behavior. It is clear enough to distinguish from siblings like create_note, but does not explicitly differentiate from update_folder or delete_folder.

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

Usage Guidelines3/5

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

The phrase "Optionally nested under a parent" implies that parent_id can be supplied to create a child folder, which is a useful usage condition. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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