Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

read_design_sidecar

Read-only

Read provenance data from the sidecar beside an STL or recipe file to inspect design history and source details. Requires Kiln Pro.

Instructions

Read provenance data from the sidecar next to an STL or recipe file.

Needs Kiln Pro.

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": {
      "stl_path": "<stl_path>"
    },
    "name": "read_design_sidecar"
  }
}

Input Schema

NameRequiredDescriptionDefault
stl_pathYesPath to the STL file. The sidecar is expected at the same path with a ``.kiln_recipe.json`` (or ``.kiln.json``) extension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / stl_path / description
      Added value: +"Path to the STL file.  The sidecar is expected at the same path with a ``.kiln_recipe.json`` (or ``.kiln.json``) extension."
  2. Addedv1.5.0

TDQS

B3.4/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. The description usefully adds that this reads from a file-adjacent sidecar rather than a server store and that it is gated behind Kiln Pro, but it does not say what happens when the sidecar file is missing or malformed.

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?

Two short sentences, front-loaded with the action and the data source; nothing is redundant. The 'Needs Kiln Pro' fragment is terse but efficient rather than padding.

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?

For a one-parameter read tool with annotations and full schema coverage, the essentials are present. The gap is that there is no output schema and the description never indicates what provenance fields come back or the shape of the response, leaving the agent unsure what to expect from a successful call.

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 parameter description already explains the .kiln_recipe.json / .kiln.json sidecar resolution. The prose adds no syntax or format detail beyond that, so the schema does the heavy lifting and 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?

States a specific verb and resource: reads provenance data from a sidecar file located next to an STL or recipe file. This distinguishes it implicitly from siblings like get_provenance_history or verify_provenance_integrity, but it never names an alternative to make the boundary explicit.

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?

The line 'Needs Kiln Pro' is a real prerequisite, which is more than most definitions offer. However, there is no guidance on when to prefer this over the other provenance tools in the sibling list, nor what to do when a sidecar is absent.

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