Skip to main content
Glama
Qwinty
by Qwinty

create_space

Set up a new workspace in Anytype to organize content and collaborate with others. Create a fresh organizational container for your objects and data.

Instructions

Creates a new Anytype space with the specified name. This tool allows you to set up a fresh workspace for organizing objects and collaborating with others. Use this tool when you need to establish a new organizational container for your Anytype content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new space

Implementation Reference

  • The handler function for the 'create_space' tool that makes a POST request to the Anytype API /spaces endpoint with the space name and returns the JSON response or handles errors.
    async ({ name }) => {
      try {
        const response = await this.makeRequest("post", "/spaces", { name });
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleApiError(error);
      }
    }
  • Zod input schema defining the required 'name' parameter as a string for the create_space tool.
    {
      name: z.string().describe("Name for the new space"),
    },
  • src/index.ts:167-188 (registration)
    Registration of the 'create_space' MCP tool using McpServer.tool() method, including name, description, input schema, and inline handler function.
    this.server.tool(
      "create_space",
      "Creates a new Anytype space with the specified name. This tool allows you to set up a fresh workspace for organizing objects and collaborating with others. Use this tool when you need to establish a new organizational container for your Anytype content.",
      {
        name: z.string().describe("Name for the new space"),
      },
      async ({ name }) => {
        try {
          const response = await this.makeRequest("post", "/spaces", { name });
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error) {
          return this.handleApiError(error);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states this is a creation operation, it doesn't mention important behavioral aspects like what permissions are required, whether there are limits on how many spaces can be created, what happens if a space with the same name exists, or what the response format looks like. For a creation tool with zero annotation coverage, this represents significant gaps in behavioral transparency.

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 efficiently structured with two sentences that each serve distinct purposes: the first states what the tool does, and the second provides usage guidance. There's no redundant information or unnecessary elaboration, making it appropriately sized and front-loaded for quick comprehension.

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?

Given this is a creation tool with no annotations and no output schema, the description provides adequate basic information about purpose and usage but lacks important contextual details about behavioral aspects, error conditions, and response format. The description covers the minimum viable information but leaves significant gaps that an agent would need to understand fully.

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 description coverage is 100%, so the schema already fully documents the single 'name' parameter. The description adds no additional parameter semantics beyond what's in the schema ('Name for the new space'). With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't need to compensate for schema gaps.

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 clearly states the specific action ('Creates a new Anytype space') and resource ('space'), distinguishing it from sibling tools like 'create_object' which creates objects within spaces rather than the space container itself. It explicitly mentions the purpose is to 'set up a fresh workspace for organizing objects and collaborating with others,' providing clear differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: 'Use this tool when you need to establish a new organizational container for your Anytype content.' This clearly distinguishes it from alternatives like 'create_object' (for creating content within spaces) or 'get_spaces' (for retrieving existing spaces), giving the agent clear context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Qwinty/anytype-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server