Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_create_project

Creates a new prompt project workspace in Devbook from a project name and optional description, giving AI assistants an organized space for managing prompt templates and related assets.

Instructions

Create a new prompt project workspace in Devbook

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the project
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 supplied, so the description carries the full burden of behavioral disclosure and doesn't meet it. "Create" implies a write, but nothing is said about permission requirements, whether project names must be unique, what happens on a duplicate, 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 zero filler or redundancy, so every word earns its place. It is arguably too terse for a mutation tool with no annotations, but that gap is better attributed to completeness than to verbosity.

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?

The tool is simple (2 flat params, fully schema-documented, no output schema), so the description covers the essentials of what it does. For a creation mutation with no annotations and no output schema, it should still say what comes back (e.g. a project ID) or what happens on failure — neither is present.

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 both `name` and `description` are already documented in the schema, establishing the baseline of 3. The description adds no extra meaning such as name constraints beyond minLength, formatting rules, or how `description` is used downstream.

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 states a specific verb and resource ("Create a new prompt project workspace") plus the product scope (Devbook), which is enough to separate it from devbook_create_prompt and devbook_get_project. However, it never explicitly names or contrasts a sibling, so it stops short of 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?

There is no when-to-use guidance, no prerequisite statement (e.g. whether a workspace or account must exist first), and no pointer to devbook_update_project or devbook_create_prompt for related operations. The only usage signal is the implicit fact that this is the creation entry point.

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