Skip to main content
Glama
Sign In

The Deployer

by com.thedploy
OverviewDiscussionsAdmin

One code problem in full

fix
Read-onlyIdempotent

One fix request: the goal and rules (The Deployer's brief), and the evidence, which is what the build or app printed, fenced and marked as data from the repository and logs. Changes nothing.

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": {
      "id": "<id>"
    },
    "name": "fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe fix request's id, fr_...
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, and 'Changes nothing' merely restates that. The genuinely additive detail is that the evidence is fenced and marked as data from the repository and logs — useful for treating retrieved content as data rather than instructions. It says nothing about what happens with an unknown id, permissions, or the workspace override.

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?

A single front-loaded sentence that gets to the payload contents immediately. The parenthetical '(The Deployer's brief)' and the nested clause about fencing add a bit of grammatical drag but no wasted sentences.

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?

There is no output schema, so the description must convey what comes back — and it does (goal, rules, evidence). Combined with annotations covering the safety profile, an agent has enough to call and interpret this tool; error behavior is the main missing piece.

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 both parameters (id, workspace) are documented in the schema, so the baseline of 3 applies. The description adds no semantics of its own for either parameter, not even that `id` is the fr_ id obtained from `fixes`.

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 makes clear this returns a single fix request's contents (goal/rules plus build or app evidence), which distinguishes it from the list-style sibling `fixes` and from state-changing siblings like `claim_fix` or `report_fix`. The trailing 'Changes nothing' confirms it is a pure retrieval. It is phrased as a noun phrase rather than an explicit verb, so the retrieval action 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 Guidelines2/5

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

No guidance on when to call this versus `fixes`, `fix_status`, or `claim_fix`. An agent must infer that this is the 'read one in full' step, and there is no mention of prerequisites such as having an fr_ id from the listing tool.

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