Skip to main content
Glama

Set space files' kind

set_space_file_kind
DestructiveIdempotent

Switch space files between study material and space info: convert study files to info to remove their facts, or convert info files to study to build facts.

Instructions

Switch one or more space files between study material and space info. Study → info removes their facts; info → study builds them. A file that can't be switched is listed under refused; the others still switch.

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>",
      "file_ids": "<file_ids>",
      "kind": "<kind>"
    },
    "name": "set_space_file_kind"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes"study" = study material turned into graph facts (notes, readings, transcripts, recordings); "info" = space info the teacher can read but that never becomes facts (a syllabus, a schedule, logistics).
file_idsYesThe files to switch (ids from read_space with files: true).
space_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior5/5

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

The annotations only flag destructiveHint=true; the description goes further by spelling out exactly what is destroyed ('Study → info removes their facts') and what is rebuilt ('info → study builds them'). It also discloses partial-failure semantics — unswitchable files land under 'refused' while the rest still switch — which an agent could not infer from annotations or schema.

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 operation, the per-direction side effects, and the partial-failure result. Nothing is repeated from the schema or annotations and the key destructive consequence is front-loaded.

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 destructive, non-idempotent-looking batch mutation with no output schema, the description covers the two things an agent most needs: what data is lost and how partial failures are reported. Remaining gaps are minor — whether removed facts are recoverable, and what `space_id` identifies.

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 67% and the `kind` enum is already documented at length, including the study/info definitions. The description adds consequence-level meaning to the direction of `kind`, but says nothing about `space_id`, which has no schema description, and adds no detail on `file_ids` beyond what the schema states.

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?

States a specific verb and resource ('Switch one or more space files between study material and space info') and immediately defines both conversion directions. The operation is distinctive enough to separate it from add_space_file or remove_space_file, though no sibling is named explicitly.

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?

The two directions imply when the tool applies (promoting info to study to build facts, demoting study to info to strip facts), so usage is inferable. There is no explicit 'use this instead of X' guidance, no prerequisite or permission note, and no statement about when not to use it.

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