Skip to main content
Glama
Sign In
Maito MCP Server

Maito MCP Server

Official
by maito-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_space

Creates a new top-level container within a workspace to organize tasks, notes, or projects.

Instructions

Create a new space (top-level container) within a workspace.

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

Input Schema

NameRequiredDescriptionDefault
iconNo
nameYes
colorNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses no side effects, permissions required, or any behavioral details beyond the basic action. For example, it doesn't state if space creation is immediate or if there are limits.

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?

The description is a single sentence with no wasted words. However, it may be too terse, lacking essential details.

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

Completeness1/5

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

Given 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how parameters interact, or any constraints (e.g., unique names).

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

Parameters1/5

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

Schema description coverage is 0% and the tool description adds no information about parameters like 'icon', 'name', 'color', or 'workspaceId'. The agent gains no understanding of what these parameters represent or their constraints.

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 explicitly states the action ('Create'), the resource ('space'), and provides context ('top-level container within a workspace'). It clearly distinguishes from sibling tools like 'create_board' or 'create_card'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. For instance, it doesn't mention prerequisites like 'workspaceId' is needed, nor does it suggest using 'list_spaces' first.

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

Deploy Server

Other Tools