Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cloud_sync_configure

Destructive

Configure and start cloud sync by setting the endpoint URL, API key, and sync interval so Kiln designs and printer data stay synchronized.

Instructions

Configure and start cloud sync.

        Args:
            cloud_url: Base URL of the cloud sync endpoint.
            api_key: API key for authentication.
            interval: Sync interval in seconds (default 60).

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": {
      "cloud_url": "<cloud_url>",
      "api_key": "<api_key>"
    },
    "name": "cloud_sync_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesAPI key for authentication.
intervalNoSync interval in seconds (default 60). Default: 60.0.
cloud_urlYesBase URL of the cloud sync endpoint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / api_key / description
      Added value: +"API key for authentication."
    • addedInput schema / properties / cloud_url / description
      Added value: +"Base URL of the cloud sync endpoint."
    • changedInput schema / properties / interval / description
      Previous value: -"Default: 60.0."New value: +"Sync interval in seconds (default 60). Default: 60.0."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / interval / default
      Removed value: -60
    • addedInput schema / properties / interval / description
      Added value: +"Default: 60.0."
  3. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower, but the description adds nothing about what is overwritten when reconfiguring, whether the API key is persisted, or what happens to an in-progress sync. 'Start' implies an ongoing background process but the implications are unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and clean, but the Args block duplicates schema text word for word, padding the definition without adding value. It is not bloated enough to be harmful, just redundant.

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

Completeness2/5

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

For a destructive mutation tool with no output schema, the description says nothing about the result of configuration (success indicator, sync state, errors on bad URL/key) or about reversibility. An agent calling this has no expectation of what comes back.

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 Args block merely restates the same three parameter descriptions verbatim with no added meaning. Baseline 3 applies since the schema carries the full burden.

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?

The description states a specific verb phrase ('Configure and start') and resource ('cloud sync'), so the basic action is clear. However, it does not distinguish this tool from close siblings such as cloud_sync_now, cloud_sync_status, or cloud_backup_configure, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this instead of cloud_sync_now (immediate sync) or cloud_sync_status (inspection), nor any prerequisite such as needing credentials stored first. The agent gets no routing guidance at all.

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