Skip to main content
Glama

Share a document

tp_share_document
DestructiveIdempotent

Sets who can open a document and returns the sharing mode, URL and reader list. Use it when the user asks to share, publish or unshare a document, to make it private, or to add or remove a reader. Modes: "link" (anyone with the URL), "people" (the listed addresses, who sign in to read it) and "private" (revokes the link; a URL already sent stops working). "link" and "people" require confirm: true; without it nothing changes and the response describes what would be disclosed. "private" needs no confirmation. For "people", emails replaces the reader list, and add and remove change individual addresses. Addresses new to the list are emailed a link.

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

Input Schema

NameRequiredDescriptionDefault
idYesDocument id from tp_list_documents.
addNoAddresses to add to the current reader list for mode "people". They are emailed a link.
modeYesWho can open it: private, link or people. Required.
emailsNoThe complete reader list for mode "people"; it replaces the current list.
removeNoAddresses to remove from the current reader list for mode "people".
confirmNoRequired when `mode` is "link" or "people". Set true after the user has agreed to that audience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes further: it explains that a link already sent stops working under private, that new addresses are emailed, and that without confirm nothing changes and the response previews the disclosure. That is exactly the extra behavior an agent needs.

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?

Front-loaded purpose sentence followed by usage, then modes, then confirmation rules. Dense but highly relevant; a slight compression opportunity exists in the mode definitions, but nothing is wasted.

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

Completeness5/5

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

Covers return values, mode semantics, confirmation behavior, side effects (emails sent, links revoked), and parameter interplay, for a destructive 6-parameter tool with no output schema. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds meaning: emails replaces the list while add/remove mutate individual addresses, and confirm is required only for link/people. This clarifies interaction between parameters that the schema documents individually only.

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?

States a specific verb+resource (sets who can open a document) and what it returns (sharing mode, URL, reader list). Clearly distinguished from siblings like tp_share_folder and tp_get_document.

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

Usage Guidelines5/5

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

Explicitly lists the triggering user intents (share, publish, unshare, make private, add/remove reader) and ties each mode to a concrete audience meaning. The private/link/people distinctions and the confirm requirement give an agent a complete decision rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.