Skip to main content
Glama

Upload a dynamic application

begin_dynamic_deployment
Idempotent

Reserves an upload for a source ZIP and validated runtime manifest on an exact existing application project. Returns the upload URL and deployment ID. Environment discovery adds new variable names disabled.

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_dynamic_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestNoRead runtime_contract first. Omitted settings retain the existing project configuration. PHP start is empty for the managed server.
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
size_bytesYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
environment_keysNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the return payload (upload URL and deployment ID) and the environment-discovery behavior where new variable names are added disabled. It still omits what happens on a revision mismatch and whether this reserves quota or expires, which matter for a non-destructive mutation.

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?

Three short sentences with the primary action and return value front-loaded, and no filler. The closing sentence about environment discovery is telegraphic ('adds new variable names disabled') and takes a re-read to parse, which keeps it below a 5.

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?

For an 8-parameter tool with a deeply nested manifest object and no output schema, the description does cover the return contract and the core reservation behavior. However, it leaves the overwrite/conflict path and the relationship to finalize_dynamic_deployment unexplained, which are exactly the ambiguities an agent would hit in a complex multi-step deployment flow.

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 75% and the schema itself is unusually self-explanatory, including guidance to read runtime_contract first, resolve project_id, and reuse idempotency_key. The description only adds that the manifest must be 'validated' and that environment_keys surface as disabled variables; it says nothing about overwrite_revision, overwrite_confirmation, or expected_revision reconciliation, which are the riskiest parameters.

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 an upload for a source ZIP and validated runtime manifest' on an 'exact existing application project'. An agent knows precisely what this call does, but the description never names how it differs from close siblings like begin_deployment or begin_project_source, which is the remaining gap for a 5.

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?

Usage is only implied by the verb 'Reserves' plus 'Returns the upload URL and deployment ID', which suggests a begin-upload-then-finalize sequence. There is no explicit statement of when to choose this over begin_deployment or begin_project_source, and no mention of prerequisites such as calling runtime_contract first (that guidance lives in the schema, not the description).

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