Skip to main content
Glama

Adopt Existing Project

adopt_existing_project

Scan an existing legacy codebase to generate context, PRDs, milestones, and audit tasks for onboarding and managing the project.

Instructions

Scan an existing legacy codebase (directories, package lists, readmes) and generate context, PRDs, milestones, and audit tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adopt_existing_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/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 behavioral burden, and it does disclose that this is a multi-artifact write operation that creates context, PRDs, milestones, and audit tasks. It says nothing about reversibility, whether existing context or PRD state is overwritten, prerequisites, permissions, or runtime cost on a large repo — all material for a scan-and-generate tool.

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?

One sentence, front-loaded with the imperative and the input, followed by the outputs. No filler, no repetition of the title, nothing that could be cut without losing meaning.

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

Completeness2/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 not be explained, but this is a heavy state-generating tool whose description omits everything an agent would need to call it safely: destination of generated artifacts, overwrite semantics against undeclared sibling state, and how it differs from bootstrap_project. The lone path argument also goes unexplained.

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?

The single 'path' parameter has a default of '.' but zero schema description coverage, so the description must compensate and does not. It never clarifies whether the path is the repository root, whether it is relative to the workspace, or how depth/scope is bounded.

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?

States a specific verb (scan) and resource (an existing legacy codebase), plus the concrete artifacts it produces (context, PRDs, milestones, audit tasks). This distinguishes it from pure-read siblings like project_info or read_file, but it never contrasts itself with adjacent generators such as bootstrap_project, init_context, or generate_project_brain.

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 by the phrase 'existing legacy codebase' — an agent can infer it is for brownfield onboarding rather than greenfield setup. However, there is no explicit when-to-use clause, no exclusion, and no named alternative (bootstrap_project for new projects, init_context for an already-scaffolded repo), so the routing decision is left to inference.

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