notlai-mcp

Overview Schema Source Related Servers Discussions Admin

notlai_create_tag

Create a new tag for categorizing notes. Checks existing tags to avoid duplicates and stores names in lowercase.

Instructions

Create a new tag for categorizing notes. Check existing tags first with notlai_list_tags to avoid duplicates. Tag names are stored in lowercase.

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_tag"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Tag name (e.g., "work", "ideas", "project-x"). Will be stored in lowercase.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behaviors. It mentions tag names are stored in lowercase, which is good. However, it does not describe what happens if a duplicate is created (e.g., error or silent overwrite), nor does it mention any destructive actions (though creating is not destructive). More detail on error handling would improve transparency.

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 concise sentences. It front-loads the action and purpose, then provides a usage advisory. Every sentence carries meaningful information without redundancy.

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

Completeness4/5

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

For a simple create tool with one parameter and no output schema, the description covers the purpose, parameter behavior, and a usage best practice. It does not specify success response or common errors, but for a straightforward operation, it is largely complete.

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?

The input schema covers the single parameter with examples and constraints (maxLength, minLength). The description adds the lowercase storage behavior but largely reiterates schema content. With 100% schema coverage, the description adds marginal value beyond the schema.

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 tool creates a tag for categorizing notes. It distinguishes itself from sibling tools like notlai_list_tags and notlai_delete_tag by specifying creation action. The note categorization context provides a clear purpose.

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 explicitly advises checking existing tags first with notlai_list_tags to avoid duplicates, providing a clear usage guideline. While it does not mention when not to use it, the advisory is sufficient for a simple create tool.

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