Skip to main content
Glama

create_project

Create an empty Tares project to organize specs, docs, and tickets for a piece of work, and bind the current session to it. Returns the project id and name.

Instructions

Create an empty Tares project for a piece of work you are about to spec, and tie this session to it. name is the project's handle (unique on Tares); goal is one line saying what it is for. Then write its docs with write_doc and its tickets (write_ticket; when they live in Linear or GitHub, link_tickets first). 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": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavioral facts: the project is created empty, the name must be unique on Tares, and creating it binds the current session to the project. It omits what happens on a duplicate-name failure and any permission/auth preconditions, which keeps it short of a 5.

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?

Front-loaded with the action and scope, then the follow-up workflow, with no filler sentences. The parenthetical about link_tickets is slightly embedded but carries necessary routing information.

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

Completeness5/5

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

For a two-parameter creation tool with an output schema already covering return values, the description supplies everything needed to call it correctly: parameter meaning, uniqueness constraint, empty-project semantics, and session-binding side effect.

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 0%, so the description must compensate, and it does: `name` is explained as the project handle, unique on Tares, and `goal` as a one-line statement of purpose. It does not note that `goal` is optional with an empty default while `name` is required.

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?

Specific verb+resource: "Create an empty Tares project for a piece of work you are about to spec, and tie this session to it." It also demarcates the boundary against write_doc, write_ticket, and link_tickets, so an agent knows this tool creates only the container, not content.

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?

States when to use it (a piece of work about to be spec'd) and lays out the follow-on sequence: write docs with write_doc, tickets with write_ticket, and link_tickets first when tickets live in Linear or GitHub. The routing condition for the alternative is explicit rather than implied.

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