Skip to main content
Glama

Link a folder to a space

link_space_folder
Idempotent

Link a folder to a space so supported files are added and new or edited files sync automatically while godspeed is open.

Instructions

Link a folder on this computer to a space. Its supported files are added, and from then on new files dropped there are added automatically and edited files are rebuilt (checked every minute while godspeed is open). godspeed sorts them into study material and space info itself while reading them, and never changes the folder. Use set_space_file_kind only to correct a kind.

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>",
      "path": "<path>"
    },
    "name": "link_space_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe folder's absolute path.
space_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the ongoing behavior a caller could not guess: supported files are added immediately, new files are picked up automatically, edited files are rebuilt, polling happens every minute while godspeed is open, and the source folder is never modified. The non-destructive/idempotent hints are confirmed and given concrete meaning (the folder is left untouched).

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?

The core action is front-loaded in the first sentence, with sync behavior following and the sibling correction hint last. Dense but each clause carries information; the parenthetical polling detail is the only mildly expendable element.

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?

Covers the mutation's side effects, the ongoing sync lifecycle, and the safety guarantee that the folder is unchanged — the key gaps for a write tool with no output schema. It leaves unanswered edge cases such as a nonexistent path or an already-linked folder, though the idempotent annotation partly covers re-linking.

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?

With only 50% schema description coverage, space_id is undocumented in both places, and the description does not explain what a space id is or how to obtain one. It does add meaning for path by specifying the folder must live on this computer (a local absolute path) rather than a remote or URL target, which the schema's 'absolute path' wording only partly conveys. Baseline 3 given the partial compensation.

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 — 'Link a folder on this computer to a space' — and immediately differentiates from the sibling correction tool ('Use set_space_file_kind only to correct a kind'). An agent can tell this apart from unlink_space_folder or add_space_file without opening either 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?

The description establishes the context in which to use it (pointing at an existing local folder to get its files into a space) and explicitly routes one adjacent case to set_space_file_kind. It does not spell out when to prefer add_space_file for a one-off file or when to use unlink_space_folder instead, so the routing is clear but not exhaustive.

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