Skip to main content
Glama

Scalix Cloud

by world.scalix

scalix_run_scale

Idempotent

Change the autoscaling bounds of an existing Scalix Run service without redeploying it. Raising min_instances keeps instances warm (no cold starts, higher cost); min_instances 0 enables scale-to-zero when idle. Takes effect immediately. Find service IDs with scalix_run_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesService ID (from scalix_run_list)
max_instancesNoNew maximum instance count the service may scale up to
min_instancesNoNew minimum instance count (0 = scale-to-zero when idle)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Service ID"New value: +"Service ID (from scalix_run_list)"
    • changedInput schema / properties / max_instances / description
      Previous value: -"New maximum instances"New value: +"New maximum instance count the service may scale up to"
    • changedInput schema / properties / min_instances / description
      Previous value: -"New minimum instances"New value: +"New minimum instance count (0 = scale-to-zero when idle)"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the agent knows this is a safe mutation. The description adds valuable context: 'Takes effect immediately' and behavioral consequences of min_instances (warm instances, higher cost, scale-to-zero). No contradiction with annotations.

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?

The description is four short sentences, each earning its place: purpose, behavioral trade-offs, immediate effect, and ID lookup. It is front-loaded with the core action and avoids redundancy.

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?

Given no output schema, the description adequately covers what the tool does, immediate effect, cost/performance implications, and how to obtain the required id. It could mention that omitting both bounds may be a no-op, but with annotations and 100% schema coverage, this is sufficient for an agent to select and invoke the tool correctly.

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%, with all three parameters clearly described. The description adds only minor nuance about raising min_instances (no cold starts, higher cost), but this is largely redundant with the schema's note about 0 = scale-to-zero. Baseline 3 applies because the schema already carries the parameter meaning.

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?

The description clearly states the tool changes autoscaling bounds of an existing Scalix Run service without redeploying, using a specific verb and resource. It distinguishes from sibling tools like scalix_run_deploy and scalix_run_rollback by focusing on scaling bounds and immediate effect. References to scalix_run_list further anchor its purpose.

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 implies when to use this tool: to adjust autoscaling without redeploying, and tells the agent to find service IDs with scalix_run_list. It explains trade-offs (warm instances vs scale-to-zero) but does not explicitly name alternatives or state when not to use it. The 'without redeploying it' phrase hints at the alternative.

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

All Scalix Cloud toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Tools are grouped by service prefix and generally target distinct resources/actions. A few execution surfaces could be confused (sandbox_run vs computer_exec vs fn_invoke; build_create vs fn_deploy vs run_deploy), and storage_list is overloaded for both buckets and objects, but descriptions clarify the boundaries well.

Naming Consistency4/5

The scalix_ prefix plus snake_case is used throughout, and most tools follow <service>_<verb>_<noun>. Minor deviations like scalix_search, scalix_status, and scalix_usage omit a service-domain qualifier, but the overall pattern is predictable and easy to navigate.

Tool Count2/5

53 tools is a very large surface. While the server covers a broad multi-service cloud platform, the count falls well beyond the 25+ threshold and will likely feel overwhelming; many service areas could reasonably be split into separate servers or trimmed.

Completeness2/5

Several service lifecycles have obvious gaps: the KV store has get/list/set but no delete, storage has upload/download/list but no delete for objects or buckets, functions have deploy/list/invoke but no delete/update, and cron has create but no list/delete. These missing operations create dead ends for agents managing common resources.

Resources