Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Request done-for-you help

request_done_for_you

Asks The Deployer's team to do it for the user: launch (put an app online in the user's own cloud account), launch_secure (the same, with exposed keys and other security problems fixed first) or move (move an app from another host, such as Heroku, into it). Tells the team, and returns the price, the delivery promise and the link where the user finishes the order and pays. Never charges anything.

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": {
      "offer": "<offer>"
    },
    "name": "request_done_for_you"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything the team should know, such as the current host or a deadline
repoNoThe repository, if there is one
offerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offer / enum
      Previous value: -[
-  "launch",
-  "move"
-]New value: +[
+  "launch",
+  "launch_secure",
+  "move"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the side-effecting nature is known. The description usefully adds that it notifies the team and 'never charges anything' and that payment happens later at a link, but omits whether repeated calls create duplicate requests or what the team does afterward.

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?

Front-loaded with the verb and the addressee, then the offers and the returns. It is dense but each clause carries information; 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?

With no output schema, the description correctly explains the return values (price, delivery promise, order link). A mutation tool with three params is adequately covered, though the duplicate-request/idempotency behavior remains unstated.

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

Parameters4/5

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

The description expands the meaning of the 'offer' enum far beyond the bare enum names, explaining what launch, launch_secure and move each do. The other two parameters are covered by schema descriptions, so the 67% coverage gap is largely compensated.

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 ('Asks The Deployer's team to do it for the user') and then enumerates the three offers, which also distinguishes it from the self-serve sibling tools launch and redeploy. An agent can tell this is a human-handoff request, not a direct deployment.

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?

The three offer values give clear context for which request to make and the parentheticals explain when each applies (app in user's own cloud, security-first, migration from another host). It stops short of explicitly telling the agent when to prefer the sibling 'launch' tool over this one.

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