Skip to main content
Glama

Redeploy demo

redeploy_demo
Destructive

Redeploy an existing Application demo (PR or branch) with the identity recorded on its tracking row - same branch or pull request, same image tag - so the Application's just-saved demo configuration (env defaults, throwaway database) applies to the running demo. This is how a crashed demo is relaunched after update_application_demo_config: the rollout replaces the pods with the new environment. Optional env / database arguments add per-launch overrides on top of the saved defaults. Safe in ask mode: the demo stays isolated in its TTL-reaped namespace. Identify the demo by workspace_id or namespace.

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>"
    },
    "name": "redeploy_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoExtra per-launch environment overrides as a name-to-value object, merged over the Application's saved demo defaults; these win by name. Values may carry ${SECRET_SLOT:<uuid>} sentinels and, when database is enabled, ${{ ankra.demo_database.* }} placeholders.
databaseNoOverride the Application's saved throwaway-database default for this launch.
namespaceNoThe demo namespace (ankra-demo-pr-* / ankra-demo-br-*). Optional if workspace_id is given.
workspace_idNoThe demo's workspace id. Optional if namespace is given.
application_idYesThe Application whose demo to redeploy.
container_portNoOverride the container port for this redeploy (1-65535). Use the port the demo's own logs say the container listens on (get_demo_diagnostics reports both the deployed and the detected port); omitted, the redeploy reuses the port recorded on the demo row, including any automatic runtime correction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the mechanism ('the rollout replaces the pods with the new environment') and the safety envelope ('stays isolated in its TTL-reaped namespace', 'safe in ask mode'), which softens the destructiveHint=true declaration into a bounded, namespace-scoped disruption. It does not cover rollout failure behavior or timing, so it is strong but not exhaustive.

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?

Front-loaded with the action and its identity constraint, then when-to-use, then overrides, then safety. Slightly dense in the middle ('so the Application's just-saved demo configuration... applies to the running demo'), but every sentence carries operational information.

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 6-parameter destructive mutation with a nested object and no output schema, the description covers trigger, identity, override layering, and blast radius well. It leaves the post-call outcome (rollout status, how to verify via get_demo_diagnostics) implicit, which is the main remaining gap.

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 the schema already documents env merging, the database override, and the workspace_id/namespace pairing. The description reinforces that env/database are per-launch overrides layered on saved defaults and that identification is by workspace_id or namespace, but adds no new format or precedence detail beyond the schema text.

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 ('Redeploy an existing Application demo (PR or branch)') plus the identity semantics: same branch, same PR, same image tag pulled from the tracking row. It also positions itself relative to update_application_demo_config, so an agent can distinguish it from redeploy_stack and the config-editing siblings.

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?

Gives an explicit when: relaunching a crashed demo after update_application_demo_config, with the saved defaults applied. It does not name an exclusion case (e.g., when redeploy_stack or deploy_pr_demo is the better choice for a not-yet-existing demo), so it stops short of full when/when-not coverage.

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.