Skip to main content
Glama

Put a document in a Space

spaces_share_document

Put a document in a Space so everyone in it can open it. Editors and the owner can change it; viewers read it. Name an existing spaceId, or newSpaceName to make one. Only the document owner may do this, and only into a Space where they are owner or editor. A document is in one Space at most, so this moves it.

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_share_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceIdNoAn existing Space, from spaces_list_spaces.
documentIdYesThe document id, from tools_list_documents. Any builder's document.
newSpaceNameNoMake a Space with this name instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses authorization requirements and, importantly, the side effect that the document leaves its current Space because it can be in only one at most — a consequence the annotations alone would not reveal. It also explains the resulting access roles (owner/editors can change, viewers read).

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?

Four short sentences, front-loaded with the effect and then permissions, targeting, and the move side effect. The role sentence ('Editors and the owner can change it; viewers read it') is useful context but is the least load-bearing for an agent deciding how to call the tool.

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 three-parameter mutation with no output schema, the definition covers effect, permissions, parameter targeting, and the move semantics. It does not say what the caller receives on success or how to resolve conflicts when a newSpaceName already exists, which are minor gaps rather than blockers.

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?

Schema coverage is 100% and the schema already documents each parameter's source (spaces_list_spaces, tools_list_documents). The description still adds value by framing spaceId and newSpaceName as an either/or choice for targeting an existing versus newly created Space, which the schema does not state as mutually exclusive.

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 opens with a specific verb+resource ('Put a document in a Space') and states the effect ('so everyone in it can open it'), plus the key scope rule that a document lives in one Space at most, so the operation moves it. It does not name the adjacent operations (spaces_unshare_document, spaces_transfer_document) to draw a boundary, so sibling differentiation is implied rather than explicit.

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?

It gives concrete preconditions: only the document owner may call it, and only into a Space where they are owner or editor, plus the choice between an existing spaceId and a newSpaceName. What is missing is explicit routing guidance — when an agent should unshare or transfer instead of share.

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