Skip to main content
Glama

ExducerAI GPU cloud

Automatic renewal

set_auto_renew
Idempotent

Turn automatic renewal of a deployment on or off. On, it keeps running and drawing credit past its end time until it is turned off or credit runs short, so get the user's yes first.

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>",
      "enabled": "<enabled>",
      "confirm": "<confirm>"
    },
    "name": "set_auto_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deployment id (rnt_… on a live key, snd_… in the sandbox).
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.
enabledYestrue: renew at the end of each term while credit lasts. false: end as booked.
renew_hoursNoThe renewal block in hours (default 720).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare this is a non-read-only but idempotent, non-destructive write, and the description adds the consequence the annotations cannot: the deployment 'keeps running and drawing credit past its end time until it is turned off or credit runs short'. That billing/runaway-cost behavior is exactly the context an agent needs before toggling, though the description stops short of saying what happens to an in-progress term or how renewal blocks are consumed.

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, front-loaded with the action and followed by the risk and the confirmation rule. Nothing redundant, nothing buried.

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?

For a four-parameter mutation with full schema coverage and no output schema, the description supplies the key behavioral consequence and the user-consent requirement. Only the finer mechanics of the renewal block and the effect on an already-scheduled end time are left unstated.

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% and the schema already documents id format, the confirm gate, and the enabled semantics plus the renew_hours default of 720. The description restates what 'on' means in operational terms but adds no detail on renew_hours or the id pattern, so this sits at the baseline.

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 specific verb and resource (turn automatic renewal of a deployment on/off) and pins the scope to one deployment id. That is enough for an agent to tell it apart from extend_deployment or stop_deployment without opening the schema.

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?

The closing clause 'so get the user's yes first' gives a usage prerequisite for enabling renewal, and the on/off framing implies the two directions. There is no explicit when-to-use versus extend_deployment or stop_deployment, and no statement of when not to call it.

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