Skip to main content
Glama

Move application to project

move_application_to_project
Destructive

Move an application into another project of the same organisation (the twin of ankra project move application). Needs projects.manage. The application's connected pipeline repositories follow it. Refused when the application is already in that project. Always have the user confirm the application and the destination project first; list_projects names the project ids and list_applications the application ids.

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_id": "<project_id>",
      "application_id": "<application_id>"
    },
    "name": "move_application_to_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesUUID of the destination project (from list_projects).
application_idYesUUID of the application to move (from list_applications).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the required permission (projects.manage), the side effect that connected pipeline repositories follow the application, and the failure condition when the app is already in the target project. Annotations already flag destructiveHint=true; the description adds the human-confirmation gate, which is the key behavioral safeguard. It stops short of describing the response or any irreversibility beyond the repo-follow effect.

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?

Four tight sentences with the action front-loaded, followed by permission, side effect, refusal case, and confirmation requirements in descending order of importance. No redundant restatement of the name or title.

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?

For a destructive two-parameter mutation with no output schema, the description covers permission, side effects, refusal condition, and the confirmation workflow, which is enough to call it safely. Only the return/result shape and any post-move verification step are left implicit.

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 coverage is 100% and both parameters already document their UUID type and source tool, so the description adds only marginal meaning via the same-organisation constraint on the destination. Baseline 3 applies since the schema does the heavy lifting for parameter semantics.

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?

States a specific verb and resource ('Move an application into another project') plus the scope constraint 'of the same organisation', which distinguishes it from move_cluster_to_project and other move_* siblings. The parenthetical CLI twin further pins down the operation for an agent that knows the CLI surface.

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?

Explicitly instructs the agent to have the user confirm both the application and destination project first, and names the exact prerequisite tools (list_projects for project ids, list_applications for application ids). It also states the refusal case (already in that project), giving a clear when-not condition.

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.