notlai-mcp

Overview Schema Source Related Servers Discussions Admin

notlai_share_note

Share a note by creating a public read-only link or by inviting a specific user via email with read or write permissions.

Instructions

Share a note. Without email: creates a public link (read-only). With email: shares with a specific user at the given permission level.

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>"
    },
    "name": "notlai_share_note"
  }
}

Input Schema

Name	Required	Description
`email`	No	Recipient email. If omitted, creates a public link.
`noteId`	Yes	The note ID to share
`permission`	No	Permission level for user shares (default: "read"). Ignored for public links.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.7.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Given no annotations, the description carries the full burden. It discloses that public links are read-only and that the permission parameter is ignored for public links. However, it does not describe other behavioral aspects like idempotency, effects on existing shares, or return values.

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

Conciseness5/5

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

The description is two sentences, concise and front-loaded. Every sentence provides essential information with no redundancy or fluff.

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

Completeness4/5

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

For a simple share tool with no output schema and no annotations, the description adequately covers the two main use cases and parameter roles. It could mention the return format (e.g., link for public share) but is otherwise complete for practical use.

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

Parameters4/5

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

The input schema has 100% coverage, so baseline is 3. The description adds value by explaining the behavioral difference when `email` is present vs. absent and that `permission` is ignored for public links. This goes beyond the schema's attribute descriptions.

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

Purpose5/5

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

The description explicitly states 'Share a note' and distinguishes two distinct modes: public link (without email) and user share (with email). This clearly identifies the tool's action and differentiates it from siblings like `notlai_unshare_note` or `notlai_create_note`.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use each mode: without email for a public read-only link, with email for user-specific sharing with a permission level. It does not explicitly mention alternatives or when not to use, but the context is sufficient for typical usage.

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