Skip to main content
Glama

Hand a document to another member of its Space

spaces_transfer_document
Destructive

Make another member of the document's Space the owner of the document. Use it when the reader asks to hand a document over, for example before they leave the Space. Only the current owner may do this, and the new owner must hold a role on the Space; a cohort reader does not count. Get the member's userId from spaces_get_space.

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

Input Schema

NameRequiredDescriptionDefault
documentIdYesThe document id, from tools_list_documents. Any builder's document.
newOwnerIdYesA member userId from spaces_get_space.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag the call as destructive and non-read-only; the description corroborates this by framing it as handing ownership over, and adds authorization context the annotations cannot express (caller must be current owner, target must hold a Space role, cohort readers ineligible). It stops short of stating explicitly that the previous owner loses ownership or whether the action is reversible.

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?

Three short sentences, front-loaded with the action, then the trigger, then the constraints and id source. Every sentence carries information an agent needs, with no restatement of the schema.

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 two-parameter mutation with no output schema and annotations covering the safety profile, the description covers purpose, trigger, permissions, and id provenance well. The only material omission is what happens to the outgoing owner's access and whether the transfer can be undone.

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 description coverage is 100% and both params are already documented in the schema, including the source tools for each id. The description repeats the spaces_get_space provenance for the userId but adds no format, constraint, or edge-case meaning beyond that, so the baseline 3 applies.

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 and resource: making another Space member the owner of a document. The title and first sentence make clear this is an ownership transfer, not merely granting access like spaces_share_document, so an agent can distinguish it from the sharing siblings.

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 clear when-to-use trigger ('when the reader asks to hand a document over, for example before they leave the Space') plus hard prerequisites: only the current owner may call it, and the new owner must hold a Space role, with cohort readers explicitly excluded. It points to spaces_get_space for the userId. It does not, however, distinguish this from spaces_share_document, which is the near-miss alternative an agent might otherwise pick.

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