Skip to main content
Glama

hand_project_to_crew

Assign a planned project to an AI crew to build it, specifying local repo paths and GitHub names and optional stricter merge-approval autonomy.

Instructions

Hand a planned project to the crew to build. project is its name or id. repos is one {path, name} per repo the project changes: path the folder it is checked out in on this machine, name its GitHub repo (owner/name), the repo that holds the plan first. Pass autonomy only when the person wants this project stricter than the crew, for example L3-review, where every merge waits for their yes. Says whether a crew is running and what to send it next.

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

Input Schema

NameRequiredDescriptionDefault
reposNo
projectYes
autonomyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose some real behavior: it hands work to a crew, it reports whether a crew is running and what to send next, and the autonomy override changes merge gating (L3-review means every merge waits for a yes). It does not say what happens when no crew is running, whether the hand-off is idempotent or reversible, or what permissions are required.

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 action is front-loaded in the first sentence and every subsequent sentence adds information about a parameter or the result. The backtick-dense, run-on phrasing ('one {path, name} per repo the project changes: `path` the folder...') is slightly cryptic to parse but contains no filler.

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?

An output schema exists, yet the description still tells the agent what the call reports back, and all three parameters are explained. For a hand-off tool of this complexity the remaining gaps (preconditions, failure modes) are minor and not required to invoke it 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 description coverage is 0%, so the description must compensate, and it largely does: `project` is 'name or id', `repos` is one {path, name} per changed repo with each key's meaning and the plan-holding repo ordered first, and `autonomy` is an override with an example value. It falls short only in not enumerating accepted autonomy values or saying what an omitted `repos` (default null) means.

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 first sentence gives a specific verb and resource: handing a planned project to the crew to build. It is clearly a distinct action from siblings like create_project or start_project, though it never names those siblings or states the boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it applies once a project is planned and needs building, and 'Pass `autonomy` only when the person wants this project stricter than the crew' is a genuine conditional. However, there is no explicit guidance on prerequisites (does the project need to exist/be planned first?) or on when to prefer this over create_project/start_project/hand_over.

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