Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cache_design

Caches a 3D design file to speed access and track versions, with optional labels and material metadata for organized project history.

Instructions

Cache a 3D design file for faster access and version tracking.

        Args:
            file_path: Path to the design file to cache.
            label: Human-readable label for the cached design.
            material: Intended material for this design.

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": {
      "file_path": "<file_path>"
    },
    "name": "cache_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoHuman-readable label for the cached design.
materialNoIntended material for this design.
file_pathYesPath to the design file to cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the design file to cache."
    • addedInput schema / properties / label / description
      Added value: +"Human-readable label for the cached design."
    • addedInput schema / properties / material / description
      Added value: +"Intended material for this design."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / label / default
      Removed value: -null
    • removedInput schema / properties / material / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds the intended benefit but omits caching-specific behavior an agent would want: whether re-caching the same file overwrites an existing entry, whether the file is copied or merely referenced, and what the 'version tracking' side effect actually does.

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 leading purpose sentence is short and front-loaded, which is good. The following Args block, however, is pure duplication of schema text already at 100% coverage, so roughly half the description earns no place.

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 simple one-required-parameter cache write with annotations covering safety and no output schema, the definition is nearly complete. The remaining gap is sibling disambiguation against cache_model and cache_design_with_source, which matters given how crowded this tool family is.

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 description's Args block repeats the schema strings for file_path, label, and material verbatim, adding no new meaning. It does not explain when label or material may be omitted (both are nullable), so the baseline of 3 is appropriate rather than higher.

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?

Specific verb plus resource: 'Cache a 3D design file' with a stated benefit ('faster access and version tracking'). It is clear what the tool does, but it never distinguishes itself from near-identical siblings such as cache_model, cache_design_with_source, or cache_model/get_cached_design, so an agent cannot confidently choose it over those.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. The phrase 'for faster access and version tracking' hints at motivation but does not tell the agent when to cache versus using cache_design_with_source, cache_model, or skipping caching entirely.

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