Skip to main content
Glama

Update a space

update_space
Idempotent

Rename a space, edit its description, signature or icon, or archive and unarchive it while keeping its lessons intact.

Instructions

Rename a space, change its description, signature or icon, or archive / unarchive it (archiving hides it from the space switcher but keeps everything; an archived space takes no new lessons).

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": "update_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoThe 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.
nameNo
archivedNo
space_idYes
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.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world mutation; the description adds real value on top by explaining what archiving actually does (hidden from the space switcher, content preserved, no new lessons accepted). It does not state whether omitted fields are left untouched, which is the main remaining behavioral gap.

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?

A single dense sentence with a parenthetical that front-loads the primary actions and then qualifies archiving. No filler, no repetition of the title, every clause carries information.

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 six-parameter update tool with a nested signature object and no output schema, the definition covers purpose and archive semantics but omits partial-update behavior (are unspecified fields preserved?) and permission requirements. Those are material gaps for a mutation tool with only one required parameter.

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 only 33%, and the rich descriptions live on icon and signature in the schema itself rather than in the tool description. The description does add semantics for the archived flag beyond the bare boolean, but adds nothing for space_id, name, or description beyond restating them.

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?

Names a specific verb (update) and resource (space) and enumerates the mutable attributes: name, description, signature, icon, and archived status. It is clearly distinguishable from update_space_deadline or add_space_file by the field list, 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?

Usage is implied by the enumerated fields — an agent can infer it should call this when it needs to rename or re-icon a space. There is no explicit when-not guidance, no mention of prerequisites such as ownership, and no pointer to create_space or update_space_deadline as alternatives.

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