Skip to main content
Glama

deployment_redeploy

Redeploy an existing deployment to create a new deployment from its resources, optionally selecting specific resources.

Instructions

Redeploy an existing deployment, optionally selecting specific resources. Creates a new deployment from resources of a previous deployment.

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": {
      "id": "<id>"
    },
    "name": "deployment_redeploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3/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 burden, and it does disclose one key behavioral fact: this creates a NEW deployment derived from a prior one rather than mutating the existing record. It does not say whether permissions are required, whether the source deployment is altered, whether IDs or resource sets are copied, or what the result looks like.

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?

Two compact sentences with the core action front-loaded. The second sentence partly restates the first but adds the useful clarification that the output is a new deployment, so the redundancy earns its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations and no output schema mean the description must cover everything, and it covers the core semantics but omits permissions, side effects on the source deployment, and how the advertised resource selection is specified. For a single-parameter mutation-adjacent tool, this is adequate but incomplete.

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 coverage is 0% for the single required 'id' parameter, and the description never explains that it refers to the deployment identifier, nor its format. Worse, it advertises 'optionally selecting specific resources' while the schema exposes no resource-selection parameter, leaving the agent unsure how that option is expressed.

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 states a specific verb+resource ('Redeploy an existing deployment') and clarifies the mechanics ('Creates a new deployment from resources of a previous deployment'), which separates it from deployment_create. It stops short of naming or contrasting it with any specific sibling tool.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative such as deployment_create or deployment_getById is mentioned. The only contextual cue is the implied precondition that the deployment must already exist.

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

Deploy Server

Other Tools