Skip to main content
Glama
KevinChu1110

driftnet

by KevinChu1110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add a folder

driftnet_create_folder

Create a folder in the reader’s tree so new links are sorted into it by the classifier. Provide a name and optional parent; existing items stay where they are.

Instructions

Add a folder to the reader's tree; new links will be sorted into it from then on. The description is what the classifier reads, so write it as a short rule (e.g. 'MapleStory and Artale helper tools'). Existing items are not re-sorted. Returns the new folder's id and parent. Fails if the parent does not exist or the name is empty. Renaming and deleting folders are left to the reader, on the web page.

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name as the reader will see it
parentNoParent folder id from driftnet_folders; omit for the top level
descriptionNoWhat belongs here, as a rule the classifier can follow

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-read-only, non-destructive, non-idempotent): it discloses that existing items are NOT re-sorted, states exact failure conditions (missing parent, empty name), and documents the return value (new folder id and parent). This is the kind of side-effect and error detail an agent needs.

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, each carrying distinct information (purpose, classifier guidance, non-re-sorting, return/failure behavior), with the core purpose front-loaded and 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?

Despite having no output schema, the description documents the return value and failure modes, and covers the non-obvious classifier semantics of the description field. Nothing an agent needs to invoke this correctly is missing.

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 3 is the baseline, but the description adds real meaning for the 'description' parameter by explaining it is read by a classifier and giving a concrete example rule ('MapleStory and Artale helper tools'). It also implies the parent/name constraints through the failure conditions.

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 ('Add a folder to the reader's tree') plus the immediate consequence ('new links will be sorted into it from then on'), which distinguishes it from sibling list/move tools. An agent can identify this as the folder-creation tool without opening the schema.

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?

Explicitly bounds scope by saying renaming and deleting are done by the reader on the web page, so the agent knows not to look for those here, and it points to driftnet_folders for parent ids. It does not explicitly contrast with driftnet_move, but the folder-creation context is clear.

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