Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_backup_configure

Destructive

Turn automatic cloud backup of designs off or report its current state for a configured remote; requires Kiln Pro.

Instructions

Turn automatic cloud backup of your designs on or off.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloud_backup_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNoWhich configured remote to back up to (default ``"default"`` — set one up with ``cloud_remote_add``). Default: "default".
enabledNo``false`` to turn automatic backup off. Omit it to report the current state without changing it. ``true`` is refused (``AUTO_BACKUP_TURN_ON_YOURSELF``): the person turns it on themselves in their account settings on the web.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / enabled / description
      Added value: +"``false`` to turn automatic backup off.  Omit it to report the current state without changing it.  ``true`` is refused (``AUTO_BACKUP_TURN_ON_YOURSELF``): the person turns it on themselves in their account settings on the web."
    • changedInput schema / properties / remote / description
      Previous value: -"Default: \"default\"."New value: +"Which configured remote to back up to (default ``\"default\"`` — set one up with ``cloud_remote_add``). Default: \"default\"."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds the subscription gate ("Needs Kiln Pro"), which is genuinely useful context not in the annotations. However, it never explains what the destructive aspect is — e.g. whether turning backup off abandons existing remote copies — and the fact that enabling is refused is disclosed only in the parameter schema, not here.

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 short lines, the core action front-loaded and the prerequisite separated out. There is no filler, and nothing is buried mid-sentence.

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 two-parameter mutation flagged destructive, the description covers the action and the plan requirement but leaves the destructive consequence and the relationship to adjacent cloud sync/push tools unstated. Adequate to call correctly, but an agent must read the schema to learn that true is refused.

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%, and the schema already explains the remote default and the enabled/omit/true-refused semantics in detail. The description adds nothing about either parameter, so the baseline 3 applies.

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?

"Turn automatic cloud backup of your designs on or off" names a specific resource (automatic cloud backup) and the two-state action, which is enough to separate it from siblings like cloud_push_branch or cloud_remote_list. It does not explicitly distinguish itself from near-neighbours such as cloud_sync_configure, so it falls short of a 5.

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?

"Needs Kiln Pro" gives a real prerequisite for when this tool is usable, but there is no guidance on when to choose this over cloud_sync_configure or manual push/pull flows, and no exclusion conditions. Usage context is implied by the prerequisite rather than explained.

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