Maito MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create_note

Create a note in a Maito workspace. Title required; body and workspace ID optional. Use for task management, note-taking, and planning.

Instructions

Create a new note. workspaceId required when multiple workspaces exist.

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": {
      "title": "<title>"
    },
    "name": "create_note"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No
`title`	Yes
`workspaceId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states the basic action of creating a note and a condition for workspaceId, omitting details on permissions, side effects, data format, or what happens upon creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence), but it lacks necessary information. It is not front-loaded with key details, and while short, it does not fully earn its place due to missing content.

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?

Given no annotations, no output schema, and 3 params with 0% coverage, the description is insufficient. It fails to explain what a note is, how it relates to similar tools, or what the expected outcome is, leaving the agent underinformed.

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 only partially addresses workspaceId (when required), but says nothing about body or title, which are critical for understanding how to use the tool.

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 clearly states 'Create a new note' which is a specific verb-resource pair. It mentions a key condition for workspaceId, but does not explicitly differentiate from sibling tools like add_journal_entry or create_card, relying on the tool name for distinction.

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?

The description only provides a conditional note about workspaceId when multiple workspaces exist. It offers no guidance on when to use this tool versus alternatives such as create_card or add_journal_entry, and does not mention when not to use it.

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