Skip to main content
Glama

Wake application deployment

wake_application_deployment
Destructive

Wake a parked deployment of an Application: restore the remembered replica count (or the descriptor default of 1 when none was pinned) and remove the park marker. Refused with a conflict when the deployment is not parked - there is no remembered count to restore. The counterpart of park_application_deployment.

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": {
      "application_id": "<application_id>",
      "cluster_id": "<cluster_id>",
      "namespace": "<namespace>"
    },
    "name": "wake_application_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceYesNamespace the deployment runs in.
cluster_idYesUUID of the cluster the deployment runs on.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent, destructive mutation; the description adds real substance beyond them by stating the exact state change (replica count restored, park marker removed), the fallback value of 1 when no count was pinned, and the conflict failure mode. The non-idempotent hint is consistent, since a second call would hit the conflict. It does not say whether the call waits for rollout or what permissions are required, so it falls short of a 5.

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?

Three short sentences, front-loaded with the action and its effect, followed by the failure condition and the counterpart reference. Every sentence carries distinct information with no restatement of the name or title.

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?

For a three-parameter mutation with no output schema, the description covers the state transition, the default value applied, and the error case, which is what an agent needs to call it correctly. The only gap is post-call behavior — whether the wake is synchronous or eventually reconciled — which matters given the destructive annotation.

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 100%, so all three identifiers (application_id, cluster_id, namespace) are already documented in the input schema. The description adds no parameter-level detail such as how the target deployment is identified within the namespace, so it neither compensates nor detracts. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Wake a parked deployment of an Application") and immediately defines the mechanics: restoring the remembered replica count and removing the park marker. It explicitly distinguishes itself from the sibling that does the inverse by naming park_application_deployment as its counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description makes the precondition unambiguous: the deployment must be parked, otherwise the call is refused with a conflict. It also names the counterpart tool, giving the agent a routing signal for the opposite operation. It stops short of a full when-to-use/when-not statement (e.g. no guidance versus restart_deployment or scale_deployment for non-parked workloads).

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.