Skip to main content
Glama

release_project

Reclaim a project from its builder crew after all ticket holders stop, push changes, and record progress; clears ticket assignments so the person's session takes ownership.

Instructions

The person took this project back from the crew (it is under releasing in crew_projects): call this once every builder that held its tickets has stopped, pushed what it had and written its progress, and has been retired. Tares clears the tickets' holders (stages, pull requests and working docs stay) and the person's session owns the project from then on. Then reply to the session that asked with [TF:RELEASED]. Only the orchestrator, or the person's own session when no orchestrator runs.

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": {
      "project": "<project>"
    },
    "name": "release_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it states that ticket holders are cleared while stages, pull requests, and working docs survive, that ownership moves to the person's session, and that a `[TF:RELEASED]` reply is required. That is exactly the destructive-scope detail an agent needs before mutating state. It omits failure behavior and whether the call is idempotent if repeated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The situation is front-loaded, which is good, but the prose is dense and jargon-laden ('pushed what it had and written its progress', 'Tares clears the tickets' holders'), and the precondition is buried mid-sentence. It is not padded, but it reads as internal shorthand rather than an instruction an agent can parse quickly.

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?

An output schema exists, so return values need no explanation, and the description covers preconditions, caller authorization, side effects, and required follow-up signaling. What remains missing is the identity semantics of the `project` argument and behavior when the precondition is not satisfied — gaps that matter for a state-mutating handoff.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required `project` parameter, and the description never clarifies whether it expects a project name, id, or the `releasing` entry from crew_projects. The only clue is the passing reference to crew_projects state. For a tool with zero schema documentation, the description should have closed this gap and does not.

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 names a specific operation on a specific resource: taking a project back from the crew, clearing ticket holders, and transferring ownership to the person's session. It anchors the tool in a concrete state ('under `releasing` in crew_projects'), which lets an agent recognize the situation without opening the schema. It stops short of naming the inverse siblings (hand_project_to_crew, finish_project) so the boundary is implied rather than stated.

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 an explicit precondition for invocation: call once every builder that held tickets has stopped, pushed, and been retired. It also constrains the caller ('only the orchestrator, or the person's own session when no orchestrator runs'), which is real routing guidance. It does not say what to do if the precondition is unmet or how this differs from finish_project.

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