Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Project status

status
Read-onlyIdempotent

Lists the user's projects on The Deployer, or one project: whether each is live, its live addresses, and its latest deployment and where that is. Changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
projectNoA project's id, name or repository. Leave out to list them all.
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?

The annotations already declare read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds useful context by stating that it changes nothing and by describing what information is returned, though it does not cover formatting or pagination details.

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?

The description is a single efficient sentence that front-loads the core action and scope. Every clause contributes to understanding what the tool does and what it returns.

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

Completeness5/5

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

For a low-complexity read-only tool with rich annotations and full schema coverage, the description supplies the relevant return content and scope. No output schema exists, but the description adequately explains what an agent can expect to see.

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 description coverage is 100%, so both parameters are fully documented in the schema. The description only alludes to the project filter with 'or one project' and adds no syntax or workspace-specific meaning beyond what the schema already provides.

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?

The description states a specific verb and resource: it lists the user's projects, or a single project, and enumerates the returned status details including live addresses and latest deployment location. This clearly distinguishes it from sibling tools like deployment, logs, or project by emphasizing project status inspection.

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

Usage Guidelines3/5

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

The description implies the two usage modes—list all projects or inspect one—matching the optional project parameter. However, it does not explicitly say when to choose this over sibling tools such as project, deployment, or check_repo, leaving alternatives to inference.

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