Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

prune_design_render_cache

Destructive

Deletes cached design-render PNGs older than a specified maximum age to clear stale files and free storage. Requires Kiln Pro.

Instructions

Remove cached PNGs older than max_age_days.

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": "prune_design_render_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_age_daysNoFiles older than this are deleted (default 30). Default: 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / max_age_days / description
      Previous value: -"Default: 30."New value: +"Files older than this are deleted (default 30). Default: 30."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the safety profile is known; the description adds the crucial scoping detail that only cached PNGs are removed, not designs or models, plus the entitlement requirement — both beyond what annotations convey. It omits whether deletion is irreversible or whether a dry-run/preview exists, which would matter for a destructive call.

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, no filler, with the destructive action front-loaded and the prerequisite separated on its own line. Every phrase earns its 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 single-optional-parameter destructive maintenance tool with rich annotations and no output schema, the description covers what is removed and the access requirement. The remaining gap is irreversibility/confirmation behavior, which is minor given destructiveHint is already declared.

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 max_age_days property already documents its meaning and default of 30. The description restates the parameter name without adding units, bounds, or behavior for edge values such as 0, so 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?

The description gives a specific verb ('Remove') and a precisely scoped resource ('cached PNGs older than max_age_days'), which is clearly distinct from nearby cache tools like delete_cached_model or list_cached_designs. It stops short of naming or contrasting any sibling explicitly, so an agent must infer the boundary itself.

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' is a genuinely useful precondition that tells the agent when the call will fail, but there is no guidance on when pruning is warranted (disk pressure, stale renders) or what to do instead if the user lacks Pro. Usage is implied as periodic cache housekeeping rather than stated.

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