Skip to main content
Glama

Finalize ZIP upload

finalize_deployment
DestructiveIdempotent

Checks an uploaded static ZIP’s size and SHA-256 checksum and queues publication for its existing project. Returns durable deployment progress and release information.

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": {
      "deployment_id": "<deployment_id>",
      "size_bytes": "<size_bytes>",
      "sha256": "<sha256>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "finalize_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256Yes
size_bytesYes
deployment_idYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true; the description adds real context by stating that a size/checksum validation happens and that publication is queued with durable progress tracking. However, it never explains what is destructive (e.g. whether an existing release is replaced) or what happens when the checksum does not match, which is a notable gap given destructiveHint=true.

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?

Two sentences, front-loaded with the validation action and ending with the observable result. Nothing is redundant, though the return-value sentence is vague enough that it earns slightly less than full marks.

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?

With no output schema, the description does supply a return summary ('durable deployment progress and release information'), which is adequate but thin. For a destructive, idempotent, write-adjacent finalization step, missing failure semantics and overwrite behavior leave the definition only minimally sufficient.

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 only 25% (just idempotency_key), so the description does some work by tying size_bytes and sha256 to a validation step against the uploaded ZIP. It still does not explain the expected source of the checksum, whether deployment_id must reference an existing upload, or what the idempotency key scopes over.

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 gives a concrete verb and resource: validates an uploaded static ZIP's size and SHA-256, then queues publication for its existing project. The word 'static' implicitly separates it from finalize_dynamic_deployment, but no sibling is named explicitly, so differentiation still requires inference.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The agent must infer that this follows an upload and precedes publication, and must guess whether finalize_dynamic_deployment is the right choice for non-static artifacts.

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