Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

create_tag

Creates a named tag with an optional color to organize and categorize Anchor notes for easier filtering and retrieval.

Instructions

Create a tag.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write-but-non-destructive profile is covered structurally. The description adds nothing beyond that: it does not say whether duplicate names are rejected, what permissions are required, whether the tag is immediately attached to notes, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and contains no padding, so nothing is wasted structurally. However, its brevity comes from under-specification rather than efficiency — the same length could have carried a uniqueness rule or a color format hint.

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

Completeness2/5

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

The tool itself is simple (two params, no nested objects, no output schema), so a short description is defensible, but 0% schema coverage and no output schema mean the description should at least cover the required `name` and the expected `color` value. With those gaps left entirely to an undocumented schema, the definition is not complete enough to invoke confidently.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must carry the burden and it does not mention `name` or `color` at all. It omits that `name` is required, whether names must be unique, and what format `color` takes (hex, name, enum).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a tag" only restates the tool name create_tag verbatim, adding no scope, resource detail, or distinguishing information. It does not contrast with sibling tools such as update_tag, delete_tag, or list_tags, and gives no sense of what a tag is or what creating one entails.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., tag names needing to be unique), and no reference to alternatives like update_tag when a tag already exists. The only usage signal is the implicit one carried by the verb "create."

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