AssetLab

Create project

create_project

Create a new project. Requires projects:write scope.

Input Schema

Name	Required	Description
`name`	Yes	Project name (required)
`budget`	No	Initial budget, stored as a lump-sum budget item. A project budget is the sum of its budget items: change it later with create/update_project_budget_item.
`status`	No	Status label shown in the app's Status column and filter: planning, in-progress, on-hold, completed, cancelled, or your organization's own value. Defaults to planning. Whether the project is active or archived follows current_phase; status counts only when the phase has no Means setting.
`end_date`	No	End date (ISO 8601)
`image_url`	No	Image URL
`start_date`	Yes	Start date (ISO 8601, required)
`description`	No	Description
`project_code`	No	Project code
`project_type`	No	Project type
`budget_status`	No	Budget status
`current_phase`	No	Current phase
`health_status`	No	Health status
`progress_status`	No	Progress status
`project_manager`	No	Project manager name
`progress_percentage`	No	Progress percentage (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / status / description

Previous value: -"Project status (required)"New value: +"Status label shown in the app's Status column and filter: planning, in-progress, on-hold, completed, cancelled, or your organization's own value. Defaults to planning. Whether the project is active or archived follows current_phase; status counts only when the phase has no Means setting."

changedInput schema / required

Previous value: -[
-  "name",
-  "status",
-  "start_date"
-]New value: +[
+  "name",
+  "start_date"
+]

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / budget / description

Previous value: -"Total budget"New value: +"Initial budget, stored as a lump-sum budget item. A project budget is the sum of its budget items: change it later with create/update_project_budget_item."

Changed2 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedOct 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the required projects:write scope, which is useful authorization context, but it does not describe side effects, returned identifiers, or what happens to omitted optional fields.

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?

The description is two short sentences and is front-loaded with the core action followed by the required scope. It is efficient and free of filler, though the first sentence largely restates the tool name and title.

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 schema fully documents all 15 parameters and annotations cover the safety profile, so the description need not repeat those. However, for a create tool with no output schema and many sibling creation tools, it does not explain return behavior or distinguish when to create a project versus creating related project sub-entities.

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 every parameter is already documented in the input schema. The description adds no parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate for a fully covered schema.

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 clear verb and resource: 'Create a new project.' This distinguishes it from the many create_project_* sibling tools, which create related entities rather than the top-level project. However, it does not explicitly differentiate itself from update_project or list_projects beyond the verb.

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 only guidance is the authorization prerequisite 'Requires projects:write scope.' There is no indication of when to use this tool versus alternatives, such as create_project_phase or bulk_create, nor any exclusions or contextual triggers.

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

All AssetLab tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?