Skip to main content
Glama

ExducerAI GPU cloud

Run a deployment longer

extend_deployment
Idempotent

Add hours to the term of a deployment that is requested, queued, provisioning or running. Same machine, same SSH details; billing stays per minute. Tell the user the extra cost (hours × gpu_count × rate) and get a yes first. Retry-safe: see idempotency_key.

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": {
      "id": "<id>",
      "hours": "<hours>",
      "confirm": "<confirm>"
    },
    "name": "extend_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deployment id (rnt_… on a live key, snd_… in the sandbox).
hoursYesHours to add. The new end may not be more than 720 hours away.
confirmYesMust be true. It states that the user approved this exact action after seeing what it does and costs. With a sandbox key (tml_test_…) nothing is real and it may be set freely.
idempotency_keyNoOptional. 8 to 128 characters. Reuse the same value when retrying the same request. Left out, one is derived from the request and the UTC date, so the identical request the same day returns the first answer; pass a new value to really do it a second time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: machine identity and SSH details are preserved, billing remains per-minute, the cost is hours × gpu_count × rate, and user consent is mandatory. The annotations already cover readOnly/idempotent/destructive, so this is solid; it stops short of saying what happens if the deployment expires mid-call or whether an extension can be undone.

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?

Four short, front-loaded clauses in escalating order — what it does, what is preserved, what to charge, and retry safety. No filler, and the confirmation requirement appears before the retry note where an agent would act on it.

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?

Covers the mutation's safety profile, cost disclosure, and retry semantics for a tool with no output schema; the notable omission is what the call returns (e.g. the new end time) and how errors surface if the deployment left an eligible state.

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 coverage is 100%, so all four parameters are documented in-schema, including the 720-hour cap and the idempotency_key derivation behavior. The description only gestures at hours and idempotency_key, adding no syntax or semantic detail the schema lacks, so baseline 3 applies.

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 precise verb and resource ('Add hours to the term of a deployment') and enumerates the eligible states (requested, queued, provisioning, running), which separates it from stop_deployment or a new create_booking without naming either.

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 a clear precondition (deployment must be in one of four states) and an explicit operating procedure: quote the extra cost and obtain user approval before calling. It does not explicitly contrast extending with creating a fresh deployment, which is the main close alternative.

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.

Resources