Skip to main content
Glama
SobieskiCodes

MCP-Claude Code Bridge

create_project

Create a new project directory with a specified name and optional description to organize coding tasks within the Claude Code Bridge environment.

Instructions

Create a new project directory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description

Implementation Reference

  • The main implementation of createProject that creates a project directory and README.md file. It takes a project name and optional description, creates the directory in the working directory, writes a README with the project details, and returns a success message.
    async createProject(name, description = '') {
      const projectPath = path.join(this.workingDir, name);
      await fs.ensureDir(projectPath);
      
      // Create a basic README
      const readmeContent = `# ${name}\n\n${description}\n\nGenerated by Claude Code Bridge\n`;
      await fs.writeFile(path.join(projectPath, 'README.md'), readmeContent);
    
      return {
        content: [
          {
            type: "text",
            text: `Project '${name}' created at ${projectPath}`
          }
        ]
      };
    }
  • Tool schema definition for create_project that specifies the input parameters (required 'name' string and optional 'description' string) and the tool description.
    {
      name: "create_project",
      description: "Create a new project directory",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Project name"
          },
          description: {
            type: "string",
            description: "Project description"
          }
        },
        required: ["name"]
      }
    },
  • server.js:138-139 (registration)
    The registration point that routes the 'create_project' tool call to the createProject method, passing the name and description arguments.
    case 'create_project':
      return await this.createProject(args.name, args.description);
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. 'Create a new project directory' implies a write/mutation operation, but the description doesn't disclose what 'create' entails (e.g., where it's created, permissions needed, whether it overwrites existing directories, or what happens on failure). This leaves significant behavioral gaps for a mutation tool.

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?

The description is a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'create' entails operationally, what the expected outcome is, or any error conditions. Given the complexity of creating resources and the lack of structured behavioral data, more context is needed.

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?

The schema description coverage is 100%, with both parameters ('name' and 'description') clearly documented in the schema. The description adds no additional parameter information beyond what the schema already provides, so it meets the baseline for high schema coverage without adding value.

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 action ('Create') and the resource ('new project directory'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'claude_code_task' or 'run_command' which might also involve project-related operations, so it doesn't achieve full sibling differentiation.

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. There's no mention of prerequisites, when this tool is appropriate versus other sibling tools, or any contextual limitations. The agent must infer usage from the tool name alone.

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

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/SobieskiCodes/claude-desktop-mcp-to-claude-agent'

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