Skip to main content
Glama

Create a space

create_space

Create a study space for a course, certification, or language and record level, source, notation, and goals so the teacher can tailor each lesson.

Instructions

Create a space for one thing the learner is studying (a university course, a certification, a language). The description is shown to the teacher in every lesson of the space: level, the book or source they follow, its notation, what they are working toward (a course's exams, an interview). Add the space's deadlines with add_space_deadline.

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": {
      "name": "<name>",
      "icon": "<icon>"
    },
    "name": "create_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconYesThe space's subject icon in the space switcher: "cpu" Computer science, "code" Programming, "sigma" Math, "chart-line" Statistics, "atom" Physics, "flask-conical" Chemistry, "dna" Biology, "brain" Psychology, "landmark" History, "scale" Law and politics, "trending-up" Economics, "globe" Geography, "languages" Languages, "book-open" Literature, "palette" Art, "music" Music. Pick the closest subject.
nameYesThe space's name, e.g. "MATH 20C – Calculus III" or "Conversational Spanish".
signatureNoThe space's signature: ONE line that sums up the subject, shown huge on the space's cover. kind "math" = LaTeX without $ (math, physics, chemistry, economics), "code" = a line of code (programming spaces), "text" = anything else (a line from a primary source, a sequence, a date). At most 60 characters. Pick something iconic for the subject; ask the learner when unsure.
descriptionNoWhat the teacher should know about the space, in the learner's terms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavioral context by explaining that the description field is shown to the teacher in every lesson, but it does not cover duplicate handling, permissions, or what the tool returns.

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?

The description is front-loaded with the core action, then explains the key field, then points to the related deadline tool. Every sentence serves a purpose and there is no redundant wording.

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?

Given the rich input schema and annotations, the description is largely complete for a create tool. It covers purpose and the most semantically important field, though it does not mention return behavior or duplicate-name handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful guidance for the description parameter by specifying what to include: level, book or source, notation, and the learner's goal, which goes beyond the schema's brief field description.

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?

The description uses a specific verb and resource: "Create a space." It scopes the tool to "one thing the learner is studying" and gives concrete examples such as a university course, certification, or language, so an agent can distinguish it from update or read operations.

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?

It clearly indicates the context for creating a space and points to add_space_deadline for deadlines. It does not explicitly say when not to use this tool or name update_space as the alternative for existing spaces, so it stops short of full when/when-not guidance.

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