Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_cached_model

Destructive

Removes a cached 3D model's file and metadata from local storage by cache ID, helping clear stale or unneeded models.

Instructions

Remove a model from the local cache (file and metadata).

        Args:
            cache_id: The unique cache ID of the model to delete.

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": {
      "cache_id": "<cache_id>"
    },
    "name": "delete_cached_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
cache_idYesThe unique cache ID of the model to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / cache_id / description
      Added value: +"The unique cache ID of the model to delete."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds that both the file and the metadata are removed, which slightly widens the scope beyond the annotations, but it says nothing about whether the deletion is reversible or what the tool returns.

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

Conciseness4/5

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

The description consists of one front-loaded sentence. The trailing 'Args:' block duplicates the schema, so that block is redundant, but it is short and does not bury the main point.

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?

This is a simple tool with one required parameter and no output schema, and its annotations already cover the destructive behavior. The description is complete enough for an agent to call it correctly. The one gap is the lack of guidance on when to use it instead of a sibling tool.

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%, so cache_id is already fully documented in the schema. The description repeats that same wording and adds no new information about the ID format or how to obtain one. A baseline score of 3 is therefore appropriate.

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 gives a specific verb and resource: 'Remove a model from the local cache (file and metadata)'. That clearly distinguishes it from cache-reading siblings such as list_cached_models and get_cached_model. The only gap is that no sibling is named explicitly.

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?

The description never says when an agent should call this rather than leave a cached model in place, nor does it mention alternatives like prune_design_render_cache or re-caching with cache_model. The only implied guidance is the warning in the word 'delete'.

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