Skip to main content
Glama

Fork Project

fork_project

Fork a project (main or any fork) into a new branch with its own database branch and test keys, when the user asks to fork, branch, or try changes away from the project.

  • Forks at once; no confirmation.

  • copyFlootDb (default "full"): "full" the parent's data. "schema": same tables, no rows. "pointInTime" + databaseAt (ISO 8601 with zone): the parent's database as it was then (code, files, keys stay current), to recover older data.

  • isolated true (only if asked): empty tables; no real data, keys or stored files (the /_cdn/static assets still show).

  • scratch true: a throwaway branch (QA run, rehearsal, backup copy): cannot be merged, deleted after 7 idle days unless kept.

  • ref: your own text for the branch (≤200 chars, e.g. a task link); list_branches shows it.

  • Output: fork project id and preview link. Merge back with compare_branches, then start_merge. Code that breaks on a fork: get_guides("fork").

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": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "fork_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
nameYes
scratchNo
isolatedNo
projectIdYes
databaseAtNo
copyFlootDbNo
suggestedCopyFlootDbNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ref
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well past the annotations: it discloses that forking happens immediately with no confirmation, that scratch branches are deleted after 7 idle days, that isolated branches omit real data but still serve /_cdn/static assets, and what the output contains. The one gap is that it never states permission or ownership prerequisites for forking an arbitrary project.

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

Conciseness5/5

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

Front-loads the core action, then uses tight bullets per parameter with zero filler; each line carries distinct information (timing, data semantics, retention, output, next step). The telegraphic style is dense but every sentence earns its place.

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?

No output schema exists, yet the description explicitly states the return ("fork project id and preview link"), and it covers the risky/irreversible aspects (auto-fork, 7-day scratch deletion) that an agent must know before calling. Only the unmentioned suggestedCopyFlootDb parameter keeps it from being flawless.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does a good job on copyFlootDb (all three enum values explained with data semantics), isolated, scratch, ref, and the databaseAt pairing. However, suggestedCopyFlootDb is never mentioned, and projectId/name get no treatment at all, leaving part of an 8-parameter schema undocumented.

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?

Names a specific verb and resource ("Fork a project (main or any fork) into a new branch") and immediately scopes the result ("with its own database branch and test keys"), which separates it from create_project or add_dependency without opening either schema.

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?

Gives an explicit trigger ("when the user asks to fork, branch, or try changes away from the project") and names the follow-on path for completing the workflow ("Merge back with compare_branches, then start_merge"). It also routes a specific failure case to a sibling: "Code that breaks on a fork: get_guides('fork')".

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources