Skip to main content
Glama

Unlink a space's folder

unlink_space_folder
DestructiveIdempotent

Detach a folder from a space to remove its files and facts from that space without modifying the folder itself.

Instructions

Unlink the space's folder: its files leave the space together with their facts. The folder itself is not touched.

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": {
      "space_id": "<space_id>"
    },
    "name": "unlink_space_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the blast radius: files leave the space along with their facts, while the folder itself survives. That is genuinely useful context beyond the structured hints, though it omits re-linkability (does link_space_folder restore the facts?) and whether an authority level is required.

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?

Two short clauses, front-loaded with the action and immediately followed by the consequence and the carve-out. Nothing is padded and the key constraint lands before the agent stops reading.

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 mutation with annotations present and no output schema, the description covers the important effect and the non-effect. The remaining gap is recoverability: it does not say whether a subsequent link reverses the removal of facts.

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?

There is one parameter (space_id) at 0% schema description coverage, so the description carries the burden. It implies the space owns a single folder, which explains why no folder identifier is taken, but it never states that space_id identifies the target space or what format it takes.

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 pairs a specific verb ("unlink") with a specific resource ("the space's folder") and states the effect on the files. It does not name the inverse sibling link_space_folder, so the differentiation is left implicit 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 Guidelines3/5

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

Usage is only implied: an agent can infer this removes a folder association from a space. There is no explicit when-to-use condition, no statement of prerequisites, and no guidance on when to prefer unlinking versus other space-mutating siblings such as update_space or remove_space_deadline.

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