Skip to main content
Glama

Make a Space

spaces_create_space

Make a shared Space owned by the user, optionally with its first notes in order. Names are unique per owner.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe Space name.
slugsNoNotes to start with, in order.
descriptionNoOne sentence on what the Space is for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish a non-read-only, non-destructive, closed-world mutation, so the description only needs supplemental context. It supplies that: the Space is user-owned, names must be unique per owner (implying a collision failure mode), and initial notes are attached in the supplied order.

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?

Two sentences, front-loaded with the action and trimmed of filler. The uniqueness sentence is compact and useful, though it is slightly terse and could read as ambiguous without the 'per owner' qualifier already present.

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 straightforward three-parameter creation tool with annotations present, most of what an agent needs is covered. However, with no output schema, the description never says what creation returns (e.g., a Space id needed for follow-up calls like spaces_add_note or spaces_invite_members), and it omits permission/ownership prerequisites.

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 100%, so the schema already defines name, slugs and description with examples. The description only echoes the ordering of 'slugs' and the uniqueness of 'name'; it adds no format, validation, or cross-parameter semantics beyond the schema, so the baseline 3 applies.

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?

The description uses a concrete verb and resource ('Make a shared Space') and adds scope details: owned by the user, optional initial notes, unique names per owner. It is clearly distinguishable from the read/leave/invite siblings by the creation verb, though it never names a sibling 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 only implied by the creation verb; there is no explicit statement of when to create a new Space versus joining an existing one, nor prerequisites such as permissions. The 'names are unique per owner' line functions as a constraint, not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources