Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Launch a project

launch
Destructive

The first (or a full) deployment of a project into the person's cloud, once a hosting plan is selected. Without confirm=true it changes nothing and returns the plan and its monthly cost. With confirm=true it creates resources the person's cloud provider bills them for; it takes 5 to 20 minutes. Needs Operate access.

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": "<project>"
    },
    "name": "launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNotrue deploys; without it nothing is created
projectYesThe project's id, name or repository (owner/name).
workspaceNoA teammate's workspace id. Default: your own.
confirm_costNotrue allows a plan above the account's cost ceiling

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"true only after the person said yes to the plan and cost"New value: +"true deploys; without it nothing is created"
    • changedInput schema / properties / confirm_cost / description
      Previous value: -"true only if launch said the plan is above the cost ceiling and the person agreed"New value: +"true allows a plan above the account's cost ceiling"
    • 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. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond destructiveHint=true and openWorldHint=true, the description discloses what actually gets created and billed, the 5-20 minute runtime, the exact semantics of the confirm gate, and the permission level required. That is materially more than the annotations convey.

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?

Three sentences, front-loaded with what the tool is, then the two-branch behavior, then the cost/time/permission facts. No filler and no repetition of the schema.

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 costly, non-idempotent, open-world mutation with no output schema, the description covers the dry-run preview contents, billing consequence, duration, and auth requirement. Only the shape of the post-confirm result is left unstated, which is minor.

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%, so every parameter is already documented, including confirm and confirm_cost. The description reinforces confirm's dry-run behavior and adds that the preview returns a plan with monthly cost, but does not touch workspace or confirm_cost beyond the schema.

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 and resource: a first (or full) deployment of a project into the person's cloud. The phrasing 'first (or a full)' implicitly separates this from redeploy, and 'once a hosting plan is selected' positions it after plan_deploy, though no sibling is named explicitly.

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?

It gives clear preconditions (a hosting plan must be selected, Operate access required) and a sharp use/no-use split: without confirm it is a read-only preview, with confirm it bills real cloud resources. It never names the alternative siblings (plan_deploy, redeploy) that an agent might otherwise pick.

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