Skip to main content
Glama

Take a document out of its Space

spaces_unshare_document
Destructive

Take a document out of its Space, so it is personal to its owner again. Only the document owner may do this; the Space itself is left alone.

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": {
      "documentId": "<documentId>"
    },
    "name": "spaces_unshare_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYesThe document id, from tools_list_documents. Any builder's document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the mutation profile is known. The description adds real value beyond them: an ownership-based authorization requirement and the scope limit that the Space is untouched. It does not say whether the document stays accessible to former Space members or whether the action is reversible, which matters for a destructive operation.

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, front-loaded with the action and its outcome, then the permission constraint and scope. No filler, though the second sentence bundles two distinct facts that could be split for scanability.

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 one-parameter destructive mutation with full annotation coverage and a fully documented schema, the definition covers effect, authorization, and scope. The remaining gap is the post-condition for other users and reversibility, which an agent would want before calling a destructive tool.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter already carries its own description pointing at tools_list_documents. The description adds no format, provenance, or edge-case guidance for documentId, so the baseline 3 applies.

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 concrete verb and resource ("Take a document out of its Space") plus the resulting state ("personal to its owner again"), which separates it semantically from spaces_share_document and spaces_transfer_document. It stops short of naming a sibling or spelling out the inverse operation, so it is clear but not maximally differentiated.

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?

Gives a hard precondition that governs when the call can succeed: "Only the document owner may do this." It also bounds the effect with "the Space itself is left alone." No explicit routing to alternatives such as spaces_transfer_document or spaces_share_document, which keeps it below a 5.

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.

Resources