Skip to main content
Glama

start_project

Start a new project for work you want built by giving it a unique name and a one-line goal; it returns the project ID and name, ready for specification.

Instructions

Start a new project for a piece of work the person wants built. name is its short name, unique on Tares; goal is one line saying what it is for. It starts empty: spec it next (the spec skill), then hand it to the crew with hand_project_to_crew. Returns the project's id and name.

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

Input Schema

NameRequiredDescriptionDefault
goalNo
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses useful traits such as the project starting empty and the name being unique on Tares. It omits what happens on a duplicate name, any permission or auth requirements, and whether the creation is reversible.

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?

Three tight sentences, front-loaded with the purpose before parameter meanings and next steps. The closing 'Returns the project's id and name' partly duplicates the existing output schema, a minor redundancy in an otherwise efficient description.

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 simple two-parameter creation tool with an output schema, the description covers purpose, both parameters, the empty initial state, and the sequencing into spec/hand_project_to_crew. The main remaining gap is failure behavior around the uniqueness constraint.

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 description coverage is 0%, so the description must compensate, and it does: `name` is characterized as a short name that must be unique on Tares, and `goal` as a one-line purpose statement. It still lacks format or length constraints, but both parameters gain real meaning beyond their bare titles.

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 gives a specific verb and resource ('Start a new project for a piece of work the person wants built') and explains what the project represents, so the agent knows what is being created. It stops short of distinguishing itself from the sibling `create_project`, leaving that ambiguity unresolved.

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 states the trigger context (a person wants something built) and lays out the follow-on workflow explicitly: spec it next via the spec skill, then hand_project_to_crew. It does not say when not to use it, and notably does not clarify the boundary against the sibling `create_project`.

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