Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_cached_model

Read-only

Retrieve cached 3D model details by cache ID to inspect or reuse a previously prepared design in Kiln.

Instructions

Return details for a specific cached model.

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

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

Input Schema

NameRequiredDescriptionDefault
cache_idYesThe unique cache ID of the model.

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."
  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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that beyond the requirement of a unique cache ID; it says nothing about what "details" comprises, failure behavior for a stale/unknown cache ID, or cache lifetime. With annotations carrying the safety burden, a 3 is appropriate.

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 core sentence is short and front-loaded, and the trailing Args block is small. The Args block is nonetheless redundant with a 100%-covered schema, so a small amount of the text does not earn its place.

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?

There is no output schema, so the description carries the burden of explaining what is returned, and "details" is too vague to tell an agent whether it gets model metadata, file paths, geometry references, or generation status. For an otherwise simple single-parameter read tool the safety and parameter side is adequate, but the return-value vagueness leaves a real gap.

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 simply restates the schema text for cache_id verbatim. No additional meaning (format, source of the ID, uniqueness across sessions) is contributed, so this sits at the baseline established by a fully documented single parameter.

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 and resource ("Return details for a specific cached model"), which is clear and actionable. However, it does not distinguish the tool from nearby siblings such as list_cached_models, search_cached_models, cache_model, or delete_cached_model, 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 Guidelines2/5

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

There is no guidance on when to use this tool versus list_cached_models or search_cached_models, and no stated prerequisite (e.g., that a valid cache ID must first come from listing or searching). The only hint is the word "specific", implying retrieval by known ID, which is a weak implied usage rather than explicit guidance.

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