Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

delete_tag

Destructive

Removes a tag from Anchor notes while preserving the notes themselves, so only the tag association is deleted.

Instructions

Delete a tag. Notes keep existing; they just lose this 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": {
      "id": "<id>"
    },
    "name": "delete_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is supplied. The description adds genuinely useful context beyond that — notes survive and only the tag association is removed — but says nothing about whether the tag deletion is permanent, whether it affects shared notes, or whether permissions are required.

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?

Two short sentences with no wasted words, and the core purpose is front-loaded ahead of the side-effect clarification. Appropriately sized for a simple tool.

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 one-parameter destructive tool with annotations covering the safety profile, the description covers the main surprising behavior (notes are preserved). However, it leaves the sole parameter's meaning unexplained and says nothing about irreversibility, which is important for a delete operation.

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?

One required parameter 'id' exists with 0% schema description coverage, and the description never mentions it. An agent cannot tell from the definition whether 'id' refers to the tag id or a note id, which is a meaningful ambiguity for a delete operation.

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?

States a specific verb and resource ('Delete a tag'), which is unambiguous and clearly distinct from the create/update/list tag siblings. It does not explicitly name or contrast with an alternative, so it stops short of full sibling differentiation.

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 prerequisites, and no mention of when a different tool (e.g., update_tag to remove notes from a tag vs. deleting the tag entirely) would be appropriate. The second sentence clarifies consequences, not usage conditions.

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