Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

unshare_note

Destructive

Stop sharing a note with someone by removing a specific share. Use the note ID and share ID from list_shares to revoke access for that person.

Instructions

Stop sharing a note with someone.

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": {
      "noteId": "<noteId>",
      "shareId": "<shareId>"
    },
    "name": "unshare_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYes
shareIdYesid from list_shares

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a permanent mutation. The description adds nothing beyond that: it does not say the share is removed permanently, whether permissions are required, whether the recipient is notified, or that the underlying note survives.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though the brevity reflects under-specification rather than disciplined completeness.

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?

For a destructive, two-required-parameter mutation with no output schema and half-undocumented parameters, the definition is too thin. An agent gets no confirmation of what is destroyed, whether the note remains shared with others, or how to recover from a mistaken revocation.

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 coverage is only 50% — shareId is documented as "id from list_shares" but noteId has no schema description at all, and the description never mentions either parameter. With the schema below 50% coverage, the description was expected to compensate and does not.

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 gives a specific verb and resource ("Stop sharing a note") plus the target ("with someone"), which is enough to distinguish it from share_note as its inverse. It stops short of explicitly naming that sibling or stating that the note itself is untouched.

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 such as needing an existing share, and no pointer to related siblings like list_shares or share_note. The implied usage (revoking an existing share) must be inferred from the verb alone.

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