Skip to main content
Glama

Add a file to a space

add_space_file

Copy local documents, code, transcripts, or recordings into a space and label them as study material or reference info so your tutor can use them.

Instructions

Copy a file from this computer into a space. Supported: .md .txt, code files (.c .py .java .js and the like), plain text with no extension, .pdf .docx .pptx .epub, .vtt .srt (transcripts) and .mp3 .m4a .wav .mp4 .mov (recordings, transcribed locally with whisper.cpp). Google Docs links (.gdoc) need saving as PDF or Word first. Study files are turned into facts by you, through wait_for_work.

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

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).
pathYesThe file's absolute path.
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 this is a non-readonly, non-destructive, non-idempotent local write. The description adds real behavioral context beyond that: audio/video is 'transcribed locally with whisper.cpp' and study material is converted to facts via wait_for_work, which tells the agent the call has asynchronous downstream effects. It omits what happens on duplicate or already-existing paths, which matters given idempotentHint=false.

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?

Front-loaded with the action in the first sentence, followed by supporting detail. The format enumeration is long but earns its place as a validation checklist; the whisper.cpp parenthetical is slightly more implementation detail than an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter write tool with no output schema, the description covers inputs and post-call behavior reasonably but never says what the call returns or how to confirm success before polling wait_for_work. Duplicate-handling and overwrite semantics are also unaddressed despite idempotentHint=false.

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 fully documented in the schema, including the study-vs-info distinction. The description reinforces the study path ('turned into facts by you, through wait_for_work') and constrains path via the format list, but says nothing about space_id, the one undocumented parameter. Baseline 3 fits.

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?

Opens with a specific verb and resource: 'Copy a file from this computer into a space.' The 'from this computer' phrasing implicitly separates it from folder-linking siblings, but no sibling is named, so an agent must infer the distinction rather than read it.

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 clear operating context: an enumerated list of accepted formats plus an explicit exclusion ('Google Docs links (.gdoc) need saving as PDF or Word first'). It also hints at the downstream workflow ('Study files are turned into facts by you, through wait_for_work') but never states when to prefer this over link_space_folder or import_notes.

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