Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

create_doc

Generate and organize documents in Dart projects by specifying title, content, and folder. Streamline project management with structured documentation.

Instructions

Create a new doc in Dart. You can specify title, text content, and folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoThe title of the folder to place the doc in
textNoThe text content of the doc, which can include markdown formatting
titleYesThe title of the doc (required)

Implementation Reference

  • The handler function for the 'create_doc' tool in the MCP server's CallToolRequestSchema handler. It extracts arguments as DocCreate, calls DocService.createDoc, and returns the result as JSON text.
    case CREATE_DOC_TOOL.name: {
      const docData = args as DocCreate;
      const doc = await DocService.createDoc({
        item: docData,
      });
      return {
        content: [{ type: "text", text: JSON.stringify(doc, null, 2) }],
      };
    }
  • The schema definition for the 'create_doc' tool, including name, description, and inputSchema with properties for title (required), text, and folder.
    export const CREATE_DOC_TOOL: Tool = {
      name: "create_doc",
      description:
        "Create a new doc in Dart. You can specify title, text content, and folder.",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "The title of the doc (required)",
          },
          text: {
            type: "string",
            description:
              "The text content of the doc, which can include markdown formatting",
          },
          folder: {
            type: "string",
            description: "The title of the folder to place the doc in",
          },
        },
        required: ["title"],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the CREATE_DOC_TOOL in the TOOLS array, which is returned by the ListToolsRequestSchema handler to expose available tools.
    const TOOLS = [
      // Config
      GET_CONFIG_TOOL,
      // Tasks
      CREATE_TASK_TOOL,
      LIST_TASKS_TOOL,
      GET_TASK_TOOL,
      UPDATE_TASK_TOOL,
      DELETE_TASK_TOOL,
      // Docs
      CREATE_DOC_TOOL,
      LIST_DOCS_TOOL,
      GET_DOC_TOOL,
      UPDATE_DOC_TOOL,
      DELETE_DOC_TOOL,
      // Comments
      ADD_TASK_COMMENT_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      // Other
      GET_DARTBOARD_TOOL,
      GET_FOLDER_TOOL,
      GET_VIEW_TOOL,
    ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a new doc' which implies a write/mutation operation, but doesn't disclose permissions needed, whether it's idempotent, error conditions, or what happens on success (e.g., returns a doc ID). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action. It wastes no words, though it could be slightly more structured (e.g., separating required vs optional parameters). Every part earns its place, making it concise and clear.

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 this is a mutation tool (create) with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a doc object or ID), error handling, or dependencies like folder existence. For a 3-parameter creation tool, more context is needed to guide the agent effectively.

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 all three parameters (title, text, folder). The description adds minimal value by listing the parameters but doesn't provide additional semantics like format examples or constraints beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 the verb ('Create') and resource ('new doc in Dart'), and specifies what can be configured (title, text content, folder). It distinguishes from siblings like update_doc or delete_doc by focusing on creation. However, it doesn't explicitly differentiate from other creation tools like create_task, which would require a 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., folder existence), when not to use it, or compare it to siblings like create_task for task-related docs. This leaves the agent without contextual usage cues.

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

Related 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/its-dart/dart-mcp-server'

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