Skip to main content
Glama

thanaton_deploy_code

Deploy application source code to a project or application slot, automatically boot the workload, and route public domain traffic to the running service.

Instructions

Deploy code directly to a Thanaton project or application slot. Automatically boots the workload and routes public domain traffic to it.

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_slug": "<project_slug>"
    },
    "name": "thanaton_deploy_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoSource code of the application entrypoint (e.g. FastAPI, Flask, Express, or Next.js code)
runtimeNoRuntime environment
filenameNoEntrypoint filename (default: app.py for python, server.js for nodejs)
project_slugYesTarget project slug or ID (e.g. mohit-aiops-cloud-intelligence)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses two side effects beyond the obvious write: the workload is automatically booted and public domain traffic is routed to it, which signals external exposure. It does not say whether a redeploy replaces existing code, what happens to prior deployments, whether the call is synchronous, or what the caller receives back.

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 sentences, both front-loaded: the action and target come first, the consequences second. No boilerplate or restatement of the name, and every clause conveys information.

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 a four-parameter deployment mutation with no annotations and no output schema, the definition is adequate on what it does and what side effects occur. It leaves meaningful gaps around redeploy/overwrite semantics and return values, which matter for an agent deciding whether to call it repeatedly.

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% and each of the four parameters has its own description plus an enum for runtime, so the schema does the heavy lifting. The description adds no additional parameter meaning (e.g., how code interacts with filename defaults, or whether code is optional for redeploying an existing slot).

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 specific verb+resource ('Deploy code ... to a Thanaton project or application slot') and adds the outcome (boots the workload, routes public traffic). It does not name or contrast with the closest siblings (thanaton_run_code, thanaton_spawn_sandbox), so the agent gets a clear purpose but no explicit differentiation.

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 statement of when to choose this over alternatives such as thanaton_run_code (ephemeral execution) or thanaton_spawn_sandbox, nor any prerequisite or when-not guidance. The only hint is the adverb 'directly', which an agent must interpret on its own.

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

Deploy Server

Other Tools