Skip to main content
Glama
Sign In
Maito MCP Server

Maito MCP Server

Official
by maito-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_board

Create a new board in a space, automatically set up with Todo, In Progress, and Done columns.

Instructions

Create a new board inside a space. Spawns 3 default columns: Todo / In Progress / Done.

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": {
      "spaceId": "<spaceId>",
      "name": "<name>"
    },
    "name": "create_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
layoutNo
spaceIdYes
displayModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses a key side effect (spawning 3 default columns), but lacks information on permissions, error handling, or reversibility of the operation.

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 two sentences long, front-loaded with the main action, and contains no redundant information.

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

Completeness2/5

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

For a creation tool with 4 parameters (2 optional with enums), no output schema, and no annotations, the description is incomplete. It doesn't document the return value, the effect of layout and displayMode, or the exact behavior of default column creation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds meaning for 'spaceId' and 'name' (implied by 'inside a space' and 'name'), but fails to explain optional parameters 'layout' and 'displayMode' which have enums.

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 verb ('Create') and resource ('a new board inside a space'), and distinguishes from siblings by noting the side effect of spawning 3 default columns, which create_column or create_space do not do.

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?

The description implies usage for creating boards in spaces but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools.

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