Skip to main content
Glama

thanaton_configure_scaling

Inspect or configure compute scaling for a project: toggle Serverless scale-to-zero and Always-On execution, set RAM, vCPU count, and idle timeout to control sandbox resources.

Instructions

Inspect or configure Thanaton compute scaling: toggle between Serverless (scale-to-zero) and Always-On stateful execution, RAM allocation, and idle timeout.

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

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform ('get' or 'set')
always_onNoEnable 24/7 Always-On stateful background execution (Indie/Pro)
memory_mbNoRAM allocation in MB (e.g. 256, 1024, 4096)
project_idYesTarget project ID
vcpu_countNovCPU count (e.g. 1, 2, 4)
idle_timeout_secondsNoInactivity seconds before scaling to zero (min 15s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the two execution models (scale-to-zero serverless vs 24/7 stateful background execution) and that idle timeout drives scale-to-zero, but says nothing about cost/billing implications of Always-On, plan gating, or whether 'set' overwrites unspecified fields.

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?

A single front-loaded sentence with no filler, structured as inspect/configure followed by the configurable dimensions. Slightly dense with parentheticals, but every clause carries 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 6-parameter tool with no annotations and no output schema, the description covers the domain well but omits operational concerns an agent needs: privilege or plan requirements for Always-On, what a 'get' returns, and whether partial 'set' calls are merged or overwritten.

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 per-parameter meaning is already documented. The description adds conceptual framing by linking Always-On to 'stateful background execution' and idle timeout to scaling to zero, but adds no format, unit, or default detail beyond the schema.

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 pair ('Inspect or configure') and resource ('Thanaton compute scaling'), then enumerates the exact dimensions controlled: serverless vs Always-On, RAM allocation, idle timeout. An agent can tell what it does without opening the schema, though it gives no signal distinguishing it from the sibling mnemon_configure_scaling.

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?

'Inspect or configure' implies that get-mode reads and set-mode mutates, but the description never states when to choose this tool over a sibling or when not to use it (e.g., which project states allow toggling Always-On). The get/set split is left for the caller to infer from the enum in the schema.

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