Skip to main content
Glama

Leave a Space

spaces_leave_space
Destructive

Take the signed-in user out of a Space. Their documents in it pass to the Space owner. The owner cannot leave; they hand the Space over or delete 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": {
      "spaceId": "<spaceId>"
    },
    "name": "spaces_leave_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceIdYesThe Space id, from spaces_list_spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered; the description goes further by disclosing the consequence for the departing user's documents (ownership passes to the Space owner) and the role restriction blocking owners from leaving. That is exactly the kind of outcome information annotations cannot convey.

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, each carrying distinct information: the action, the document consequence, and the owner exception. The outcome and constraint are front-loaded after an unambiguous opening.

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 single-parameter destructive tool with full schema coverage and annotations declaring destructiveness, the description covers the key consequence and the main precondition. Only a note on confirmation or irreversibility is missing, which is minor here.

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 spaceId parameter is already documented, including the pointer to spaces_list_spaces, so the description adds no parameter meaning. 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 ('Take the signed-in user out of a Space'), including the actor scope ('signed-in user'), which separates it from a remove-other-member operation such as spaces_remove_member. An agent can identify the operation without opening the schema.

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?

Adds a clear when-not condition: the owner cannot leave and must instead hand the Space over or delete it, which points the agent toward alternative actions. It stops short of naming the specific transfer or delete tools, leaving the routing to inference.

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