Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

Deployment logs

logs
Read-onlyIdempotent

The log of a project's latest deployment, or of a given deployment, newest lines last, with secrets removed. errors_only keeps only errors and warnings. The lines are the build's and the app's own output. 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": "logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoHow many lines, newest last. Default 80.
projectNoThe project's id, name or repository. Optional with one project.
workspaceNoA teammate's workspace id. Default: your own.
errors_onlyNoOnly errors and warnings
deployment_idNoA specific deployment, instead of the latest

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real context beyond them — secrets are redacted from output, lines are ordered newest-last, and the content is the build plus app output. 'Changes nothing' merely restates readOnlyHint.

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?

Four short sentences, front-loaded with the resource and scope before the option explanations. 'Newest lines last' is duplicated from the schema and 'Changes nothing' duplicates the annotations, but the waste is minor.

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 five all-optional parameters and no output schema, the description covers what comes back (build and app output lines, newest last, redacted) and the main scoping options. It does not say what happens when the project has no deployments, which is a small remaining gap.

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 every parameter is already documented in the schema, so the description's restatement of line ordering and errors_only adds little. It implies the latest-vs-specific-deployment choice but supplies no syntax or format detail the schema lacks.

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?

Names a specific resource ('the log of a project's latest deployment, or of a given deployment') and clarifies the content ('the build's and the app's own output'), which separates it from metadata-oriented siblings like deployment or status. It never explicitly names a sibling, so differentiation is implied rather than stated.

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?

'errors_only keeps only errors and warnings' and 'a specific deployment, instead of the latest' give conditional selection cues within the tool, but there is no guidance on when to reach for this versus diagnose, deployment, or status when investigating a failure.

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