Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Set env variables

set_env

Sets (or deletes) env variable values for the service a project deploys. Values are stored encrypted and are never returned. Other values are kept. On a live project, the services whose env changed are redeployed; otherwise the values apply on the next deployment. Multi-line values are stored as credential files. 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": "set_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
deleteNoNames to remove
valuesNoNames to values, e.g. {"API_URL": "https://..."}
projectYesThe project's id, name or repository (owner/name).
serviceNoService id or name, when the project has several
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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond annotations: values are encrypted and never returned, existing values are preserved (merge semantics), live projects trigger redeployment of affected services, multi-line values become credential files, and Operate access is required. This is exactly the side-effect and permission information an agent needs before a non-idempotent mutation.

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?

Five short sentences, front-loaded with the core action and its scope, followed by storage behavior, side effects, and the auth requirement in decreasing order of importance. No filler or restatement of the 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 5-parameter mutation with no output schema but full annotation coverage, the description covers permissions, side effects, storage semantics, and merge behavior. It stops short of describing error conditions or whether redeployment is synchronous, which would matter for a live-project call.

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?

Schema description coverage is 100%, so the baseline is 3; the description still adds meaning by explaining that multi-line values are stored as credential files and that untouched values are kept, plus the encrypted/never-returned treatment of `values`. It does not elaborate on the `delete` array's interaction with `values`, leaving that one relationship to the schema.

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 (sets/deletes) and resource (env variable values) with scope clarified as 'for the service a project deploys', which also disambiguates from project-level settings. No sibling tool covers env variables, so the agent can route here without opening the schema.

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?

Gives concrete context for the two behavioral modes: on a live project the affected services are redeployed, otherwise values apply on next deployment. Also states the prerequisite ('Needs Operate access'). Lacks explicit exclusions or pointer to an alternative tool, but none of the siblings competes for this task.

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