Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Redeploy a live project

redeploy
Destructive

Puts the latest code on a live project's branch online: pulls it and restarts the app, like Pull & Restart in The Deployer. Changes a live app. Only for a project that is already live. Takes a few minutes.

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

Input Schema

NameRequiredDescriptionDefault
projectNoThe live project's id, name or repository. Optional with one project.
workspaceNoA teammate's workspace id. Default: your own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / workspace / description
      Previous value: -"Act in a teammate's workspace: its id from account. Default: your own."New value: +"A teammate's workspace id. Default: your own."
  2. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "Act in a teammate's workspace: its id from account. Default: your own.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds genuinely new context: it restarts the app (implying downtime/disruption) and takes a few minutes. It does not say whether the restart is graceful, whether in-flight traffic is dropped, or how failure surfaces, so it is additive but not exhaustive.

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 tight sentence plus two short qualifiers; the effect, precondition, and time cost are all front-loaded. Minor repetition of 'live' (live project / live app) but no filler to cut.

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 two-optional-param mutation with annotations carrying the safety profile and no output schema, the description covers effect, precondition, and duration. It leaves open what the agent gets back and what to do on failure (e.g. check status/logs), which is a modest gap rather than a blocker.

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 are documented there, so baseline 3 applies. The description only indirectly informs 'project' via 'a project that is already live'; it says nothing about the workspace parameter's meaning (deploying from a teammate's workspace).

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 concrete verb+resource ('Puts the latest code on a live project's branch online') and explains the mechanism (pulls and restarts the app), plus an analogy to a known UI action. The 'already live' qualifier separates it from launch/create_project/plan_deploy siblings.

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

Usage Guidelines4/5

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

'Only for a project that is already live' is an explicit precondition that rules out non-live projects, and 'Changes a live app' signals this is a real mutation. It stops short of naming the sibling to use instead for a not-yet-live project (e.g. launch/plan_deploy).

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

All The Deployer toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources