Skip to main content
Glama
bruhsb
by bruhsb

paperclip_create_project

Create a new project with name and optional description, status, goal link, and workspace configuration.

Instructions

Create a new project. Optionally include a workspace config.

Args:

  • name: string — Project name (required)

  • description: string (optional) — Project description (markdown)

  • status: string (optional) — Initial status (example: "active")

  • goalId: string (optional) — Goal UUID to link the project

  • workspace.cwd: string (optional) — Local working directory (example: "/home/user/repo")

  • workspace.repoUrl: string (optional) — Remote repository URL (example: "https://github.com/org/repo")

Returns: Returns the created project object with all fields including assigned UUID and workspace if provided.

Examples:

  • Use when: setting up a new feature project linked to a goal, with a workspace for agent execution

  • Don't use when: you need to add a workspace to an existing project — use paperclip_create_workspace instead

Error Handling:

  • 400: validation failure → ensure name is non-empty

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: goalId not found → verify with paperclip_list_goals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description (markdown)
statusNoInitial status (e.g. active)
goalIdNoGoal UUID to link the project to
workspaceNoOptional workspace config to create alongside the project
Behavior4/5

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

Annotations indicate non-destructive and open-world false. The description adds that the tool returns the created project object with UUID, and covers error handling for validation, auth, and not-found cases. No contradictions with annotations.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). No redundant sentences; each part provides unique information. Length is appropriate for the complexity.

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

Completeness4/5

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

Despite no output schema, the description explains the return value. Includes error scenarios. Could mention more sibling alternatives for related operations (e.g., update_project), but the coverage is solid for a create tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by providing example values for parameters (e.g., status: 'active', workspace.cwd: '/home/user/repo') and clarifying the workspace is optional and created alongside the project. This goes beyond the schema descriptions.

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 clearly states 'Create a new project' and mentions optional workspace config. It explicitly distinguishes from the sibling tool 'paperclip_create_workspace' in the 'Don't use when' section, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Provides explicit 'Use when' and 'Don't use when' guidance, including a specific alternative tool for adding workspace to existing projects. This gives the agent clear decision rules.

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/bruhsb/paperclip-mcp'

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