Skip to main content
Glama

Start ZIP deployment

begin_deployment
Idempotent

Reserves a ZIP upload for an exact existing static project with revision concurrency checks. Returns a short-lived upload URL and deployment ID.

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_id": "<project_id>",
      "size_bytes": "<size_bytes>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "begin_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
size_bytesYes
auto_activateNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
expected_revisionNoOriginal base_revision in local .deploymonster.json; never substitute current server revision before reconciliation.
overwrite_revisionNoExact remote revision the USER explicitly agreed to overwrite after seeing change summary.
overwrite_confirmationNoOnly after explicit user overwrite choice; never auto-confirm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, idempotent, non-destructive, closed-world write. The description adds the useful facts that the upload URL is short-lived and that a deployment ID is issued, plus the mention of concurrency checks, but says nothing about failure modes or the overwrite path that the schema's overwrite_* parameters expose.

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?

Two tight sentences, front-loaded with purpose and followed by the return contract. No redundant restatement of name or title.

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

Completeness3/5

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

No output schema exists, and the description correctly discloses the return values (upload URL, deployment ID). However, for a seven-parameter deployment-start tool it omits the surrounding workflow and any note that finalize_deployment completes the upload, leaving gaps an agent must guess at.

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?

With 71% schema coverage and rich per-parameter descriptions (project_id resolution, idempotency reuse, expected_revision, overwrite_confirmation), the schema does the heavy lifting. The description only gestures at project and revision semantics without adding syntax or guidance beyond it.

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?

States a specific verb and resource ("Reserves a ZIP upload") and scopes it to "an exact existing static project", which implicitly separates it from the dynamic-deployment siblings. It stops short of naming any sibling explicitly.

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 phrase "exact existing static project with revision concurrency checks" hints at preconditions, but there is no explicit when-to-use, when-not-to-use, or pointer to begin_dynamic_deployment for non-static cases. The multi-step begin/upload/finalize flow is left for the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources