Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Scale Serving

scale_serving
Idempotent

Adjust a serving's replica range, autoscaling, and per-replica price cap, previewing cost-raising changes for confirmation while applying reductions immediately.

Instructions

Change a serving's replica range, autoscaling, or per-replica price cap. Pass only the fields to change. Any change that can raise the hourly cost — a larger replica range, turning autoscale on, or a higher per-replica price cap — with confirm=false (default) only returns the current state and the requested change and changes nothing; call again with confirm=true after the user agreed. Lowering the range, turning autoscale off, or lowering the cap applies immediately. Replicas running above the new setting are removed within about 30 seconds and the requests they are handling fail: with autoscale off the serving keeps min_replicas, with autoscale on up to max_replicas. When that happens the answer has replicas_removed; if the serving is in use, tell the user before lowering it. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "serving": "<serving>"
    },
    "name": "scale_serving"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
servingYes
autoscaleNo
max_replicasNo
min_replicasNo
operation_idNo
price_cap_per_hourNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite the annotations, the description adds substantial behavior: the two-phase preview/confirm split, exactly which changes are cost-raising, that in-flight requests fail when replicas are removed within ~30 seconds, that min_replicas or max_replicas is retained depending on autoscale, the replicas_removed field, and operation_id reuse rules with timeout recovery via operation_status. Replica loss with failing requests is disclosed, which is the important nuance behind destructiveHint=false.

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?

The description is dense but well ordered: purpose first, then the confirmation rules, then the destructive side effects, then operation_id mechanics. It is longer than typical but nearly every clause conveys a decision-relevant fact; the embedded caveat about advising the user mid-paragraph is slightly awkwardly placed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, mutation-flagged tool with an output schema, this covers what an agent needs: what each field does, when a call is a preview versus a real change, the safe retry protocol with operation_id, and the user-facing consequence of downsizing. Return values are referenced only where behaviorally relevant, which is appropriate given the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden and largely does so: it explains confirm semantics, min_replicas/max_replicas, autoscale, price_cap_per_hour, and the operation_id lifecycle (reuse the preview ID or generate a UUID, keep it across retries). Only the serving identifier itself is left unexplained, though its meaning is inferable from context.

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 first sentence gives a precise verb plus resource and enumerates the exact mutable surface: 'Change a serving's replica range, autoscaling, or per-replica price cap.' This clearly separates it from sibling tools like delete_serving, deploy_serving, and pause_serving, which handle different lifecycles.

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?

Guidance is explicit about the confirmation workflow: cost-raising changes with confirm=false only preview, while lowering the range, disabling autoscale, or lowering the cap applies immediately. It also advises telling the user before lowering a serving that is in use. It stops short of naming alternatives (e.g., deploy_serving for image changes) or stating when to prefer a different tool.

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