Skip to main content
Glama

Add a folder

driftnet_create_folder

Create a folder in the reader's tree to sort new links; specify a visible name, optional parent, and a description that acts as a classifier rule.

Instructions

Add a folder to the reader's tree. New links can be sorted into it from then on; existing items are not re-sorted, so file them with driftnet_move_items. To rename or re-describe a folder that exists use driftnet_update_folder instead of creating a near-duplicate. name is what the reader sees; the id is derived from it (a lowercase slug, or a generated id for names without Latin letters) and returned. description is what the classifier reads when sorting, so write it as a rule, e.g. 'MapleStory and Artale helper tools'; without one only the name guides sorting. parent nests it under an existing folder id; omit it for the top level. Fails if the parent does not exist or a folder with that name already sits under the same 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": "driftnet_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name as the reader will see it, 1–60 chars, e.g. 'Games'
parentNoParent folder id from driftnet_list_folders; omit for the top level
descriptionNoWhat belongs here as a rule for the classifier, up to 300 chars

Output Schema

NameRequiredDescriptionDefault
idYes
parentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • changedInput schema / properties / description / description
      Previous value: -"What belongs here, as a rule the classifier can follow"New value: +"What belongs here as a rule for the classifier, up to 300 chars"
    • changedInput schema / properties / name / description
      Previous value: -"Folder name as the reader will see it"New value: +"Folder name as the reader will see it, 1–60 chars, e.g. 'Games'"
    • addedInput schema / properties / parent / maxLength
      Added value: +80
    • addedInput schema / properties / parent / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "parent": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "parent"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv0.5.1
    • changedInput schema / properties / parent / description
      Previous value: -"Parent folder id from driftnet_folders; omit for the top level"New value: +"Parent folder id from driftnet_list_folders; omit for the top level"
  3. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / description / description
      Added value: +"What belongs here, as a rule the classifier can follow"
    • addedInput schema / properties / name / description
      Added value: +"Folder name as the reader will see it"
    • changedInput schema / properties / parent / description
      Previous value: -"Parent folder id; omit for the top level"New value: +"Parent folder id from driftnet_folders; omit for the top level"
  4. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: existing items are not re-sorted, the id is derived from the name and returned, and creation fails if the parent is missing or a duplicate name exists under the same parent. This adds meaningful operational context for a non-destructive but non-idempotent mutation.

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 front-loaded with the core action and then efficiently covers alternatives, parameter meaning, and failure cases. Despite being detailed, every sentence contributes useful information and there is no filler.

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?

Given the annotations, full schema coverage, and the presence of an output schema, the description provides everything needed to call the tool correctly. It covers purpose, alternatives, parameter semantics, derived id behavior, and failure conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameters are already documented, but the description adds semantic guidance beyond the schema: `description` is read by the classifier and should be written as a rule, and `name` drives the derived id. This is useful enrichment, though the schema already carries the basic parameter definitions.

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?

The description uses a specific verb and resource: 'Add a folder to the reader's tree.' It also clearly distinguishes this from `driftnet_update_folder` for renaming/re-describing and from `driftnet_move_items` for filing existing links.

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?

It explicitly says when to use this tool versus alternatives: create for new folders, update for existing folders, and move_items for existing links. It also states when to omit `parent` and what causes failure, leaving little to inference.

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