Skip to main content
Glama

doer_create_project

Creates a new Doer project workspace to group related todo lists and checklists, so tasks stay organized by project.

Instructions

Create a new project workspace in Doer to organize related todo lists and checklists

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the project workspace
descriptionNoDetailed description of the project workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 behavioral burden. It implies a mutation but says nothing about whether the name must be unique, what permissions or account context are required, what the response contains (e.g., a new project ID), or whether the operation is reversible.

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?

A single front-loaded sentence with no filler; the create action and resource come first. The closing purpose clause is useful context rather than padding, though the phrase "in Doer" is redundant on a Doer-prefixed tool.

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?

This is a simple two-parameter creation tool, so little explanation is needed, and the schema is fully documented. However, with no annotations and no output schema, the description never tells the agent what a successful call returns, which matters for chaining the new project into subsequent calls.

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%, covering both `name` and `description`, so the baseline is 3. The description adds no format, length, or uniqueness constraints beyond what the schema already states.

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 names a specific verb and resource ("Create a new project workspace") plus its scope as a container for todo lists and checklists, which separates it from doer_create_todo_list. It stops short of naming siblings explicitly, so a 4 rather than 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 trailing clause hints at intent (organizing related lists) but there is no when-to-use guidance, no statement of when to prefer a project over a standalone todo list, and no prerequisites or exclusions. An agent must infer the choice between this and doer_create_todo_list.

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