Skip to main content
Glama

Create a project (a new bot)

dosai_create_project

Create a new project, which is one bot for one business. Works only when the assistant is connected to ALL the owner's projects (a one-project connection cannot create more). The project starts as a draft; a first project may get a free starting balance. Next: dosai_get_setup_guide with the new project_id. Returns project_id.

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>",
      "company_name": "<company_name>"
    },
    "name": "dosai_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort name the owner will see, e.g. "Dental clinic Zhemchug".
industryNoIndustry in a word or two, e.g. dentistry, beauty salon, driving school.
timezoneNoIANA time zone of the business (Area/City). Omit to use the platform default.
company_nameYesThe business name as clients know it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds meaningful behavior beyond that: the new project starts as a draft, a first project may receive a free starting balance, and creation is gated on an all-projects connection. It also discloses the return value explicitly.

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?

Four tight sentences, front-loaded with the outcome, then the precondition, the resulting state, and the mandated follow-up. No redundant restatement of the title or schema.

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

Completeness5/5

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

For a 4-parameter creation tool with no output schema, the description supplies the precondition, the post-creation state, the returned project_id, and the exact next call. Nothing an agent needs to invoke this correctly is missing.

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 name, company_name, industry, and timezone are already documented with examples and a maxLength. The description adds no per-parameter meaning beyond the domain framing of "one bot for one business"; baseline 3 is appropriate.

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 opens with a specific verb and resource ("Create a new project") and immediately defines the domain object as "one bot for one business," which lets an agent distinguish this from dosai_get_project and dosai_update_project without opening their schemas.

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

Usage Guidelines4/5

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

It states a hard precondition ("Works only when the assistant is connected to ALL the owner's projects") and names the concrete next step ("dosai_get_setup_guide with the new project_id"), which is strong routing. It stops short of naming an alternative for the blocked one-project case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources