Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

update_tag

Rename a tag or change its color in Anchor notes so labels stay accurate and visually distinct.

Instructions

Rename a tag or change its color.

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": {
      "id": "<id>"
    },
    "name": "update_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
colorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already state that this is a non-read-only, non-destructive, closed-world operation. The description adds only whether the operation renames or recolors a tag and does not cover partial-update behavior, required permissions, error cases, or what happens when only the ID is supplied.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted words. Its brevity leaves substantive behavior and parameter information out, but that is an incompleteness issue rather than a structural or concision problem.

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 three-parameter update tool with clear annotations and no output schema, the description gives the basic operation. It remains incomplete because it does not explain the required id parameter, does not clarify partial-update semantics, and offers no usage context against sibling tools.

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%, so the description must explain the three parameters. It only maps to the name and color parameters through "rename" and "color"; the required id parameter and the format or constraints for name and color are left entirely to the schema.

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

Purpose4/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: it states that this tool renames a tag or changes its color. That clearly distinguishes it from create_tag, delete_tag, and list_tags, though it does not explicitly name a sibling as an alternative.

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?

The description gives no guidance on when to use update_tag versus create_tag, delete_tag, or list_tags. It also does not state any prerequisites for updating an existing tag, such as needing the tag ID or whether the caller must already have access to the tag.

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