Skip to main content
Glama
Sign In
notlai-mcp

notlai-mcp

by lzientek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

notlai_create_folder

Create a new folder to organize your notes, allowing you to group related content together for better note management.

Instructions

Create a new folder to organize your notes. After creating a folder, use notlai_move_note to move notes into it.

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": "notlai_create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name (e.g., "Work", "Personal", "Projects")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A3.7/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 full burden. It only states the basic action and lacks details on constraints (e.g., uniqueness, permissions, error handling) or side effects.

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?

Two concise sentences, front-loaded with the primary purpose, no redundant information.

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?

For a simple single-parameter create tool, the description covers the basic usage and follow-up step. However, it omits details on return values, error conditions, and prerequisites (e.g., authentication).

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 schema already well-documents the 'name' parameter with length constraints and example values. The description adds no additional parameter meaning.

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 clearly states the action ('create') and resource ('folder') with a specific purpose ('to organize your notes'). It distinguishes from sibling tools like notlai_delete_folder and notlai_list_folders.

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?

The description provides a usage hint: after creating, use notlai_move_note to move notes. It implies context but lacks explicit when-not-to-use or alternative tool comparisons.

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