Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

share_note

Share an Anchor note with another user by ID and set or update their permission to viewer or editor.

Instructions

Share a note with another user of this Anchor server, or change their permission if already shared.

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>",
      "userId": "<userId>",
      "permission": "<permission>"
    },
    "name": "share_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYes
userIdYesid from find_users
permissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/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-not-destructive profile is covered. The description adds genuinely useful behavior beyond that: sharing is idempotent and an existing share is updated rather than duplicated. It omits error behavior (unknown user, sharing with self) and whether the recipient is notified.

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 well-formed sentence with the core action front-loaded and the upsert caveat attached. There is no padding, though the brevity contributes to the missing parameter detail.

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?

With three required parameters, no output schema, and partial schema coverage, the description should carry more weight. It says nothing about what a successful share returns, how permission changes affect existing access, or failure modes, leaving real gaps for a mutation tool.

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 only 33%: permission carries an enum, userId has a short 'id from find_users' note, and noteId has no description at all. The description does not compensate — it never explains what noteId format is expected or what the viewer/editor distinction actually permits, adding almost nothing beyond 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 names a specific verb (share) and resource (note) and clarifies the upsert behavior: it also changes permission if the note is already shared. It is distinguishable from siblings such as unshare_note or list_shares, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the verb and the 'another user of this Anchor server' scoping, so an agent can infer this is the tool for granting access. There is no explicit when-not guidance, no mention of unshare_note as the inverse, and no note on prerequisites such as needing the target user's id from find_users.

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