mcptask.online

CreateProjectTool

Create a project in an account, as the web "new project" form does. Ask the user for every value this tool returns under needs_input and never invent one, least of all a price or a currency: call with only account_code to get the questions and their allowed values, then call again with the answers. When an active project of the same name already exists, nothing is created and that project is returned (duplicate: true).

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": {
      "account_code": "<account_code>"
    },
    "name": "CreateProjectTool"
  }
}

Input Schema

Name	Required	Description
`name`	No	Project name. Ask the user.
`start_at`	No	Optional start, ISO 8601. Default now.
`description`	No	What the project is about. Ask the user.
`is_template`	No	Optional: true makes the project a template. Default false.
`account_code`	Yes	Account code (e.g., "bcp", "jchsoft")
`currency_code`	No	Currency code, from allowed_values under needs_input. Ask the user.
`sprint_points`	No	Optional number of points allowed in a sprint. Empty by default.
`project_type_code`	No	Project type code, from allowed_values under needs_input. Ask the user.
`company_relative_id`	No	Relative ID of the company the project is for. Needed only when the account has more than one company.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the two-phase needs_input interaction, the prohibition on inventing values, and the duplicate-name behavior where nothing is created and the existing project is returned with duplicate: true. These are important behavioral details for a creation tool with side effects, and they do not conflict with the supplied annotations.

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 front-loaded with the core action and follows with the critical call sequence and duplicate handling. It is dense but efficient; most sentences carry actionable information.

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 creation tool with no output schema, the description covers the important input flow, user-confirmation requirement, and duplicate return behavior. It does not enumerate every return field, but it gives enough context to invoke the tool correctly.

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%, so the schema already documents each parameter. The description adds procedural meaning by explaining that values returned under needs_input must be obtained from the user and that allowed values for fields like currency and project type come from that flow.

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 states a specific verb and resource: 'Create a project in an account.' It also anchors the behavior to the web 'new project' form, which clarifies scope without needing to inspect sibling tools.

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?

It gives an explicit two-step workflow: first call with only account_code to retrieve needs_input questions and allowed values, then call again with the answers. It also tells the agent to ask the user rather than invent values, especially price or currency, and explains what happens when a duplicate name exists.

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

All mcptask.online 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.

Resources

Need Help?