Weft

Create Project

create_project

Use this when the user wants a new project context (e.g. 'add a project for Organicus'). Name must be unique per board. Color defaults to a rotating palette pick; url is the project's website (its favicon is shown on task cards).

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

Input Schema

Name	Required	Description
`url`	No	Project website (favicon source)
`name`	Yes
`color`	No	Preset palette color

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed1 schema field changedOct 8, 2026

changedInput schema / $schema

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

First observedSep 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already covering the safety profile (write, non-destructive, non-open-world), the description adds real behavioral context: the name must be unique per board, color defaults to a rotating palette pick, and url drives the favicon on task cards. It omits what happens on a duplicate-name failure, which is the main remaining gap.

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?

Three sentences, front-loaded with the usage trigger, each carrying distinct information (when to use, name constraint, color/url behavior). No filler or redundancy.

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?

For a 3-param create tool with no output schema and annotations carrying the safety profile, the description covers usage, the key constraint, and default/side-effect behavior. It does not describe the return payload or error handling, which is minor given no output schema is declared.

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 67%, and the description compensates for the uncovered name parameter by stating the per-board uniqueness rule, plus it clarifies the color default behavior (rotating palette) and the url's purpose. This meaningfully extends what the schema documents (enum list, uri format).

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 the resource ('a new project context') and, together with the name/title, makes the create action unambiguous. It implicitly distinguishes from siblings like create_task/create_sprint by naming the project resource, but it never explicitly contrasts itself with them or with update_project.

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 gives a clear when-to-use trigger with a concrete example utterance ('add a project for Organicus'), which is stronger than most. It does not state exclusions (e.g. use update_project for existing projects) or any prerequisites, so it stops short of the top band.

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

All Weft tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.