Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_part_passport

Read-only

Retrieves a Part Passport for a design ID, consolidating part details into one call so agents can inspect a design without querying multiple sources. Requires Kiln Pro.

Instructions

Everything about one part/design in a single call — the Part Passport.

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": {
      "design_id": "<design_id>"
    },
    "name": "get_part_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesThe design's id (the slug under ~/.kiln/designs, the same id the Versions and Models surfaces use).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"The design's id (the slug under ~/.kiln/designs, the same id the Versions and Models surfaces use)."
  2. Addedv1.5.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the tier requirement (Kiln Pro), which is genuinely useful behavioral context, but says nothing about the size, shape, or cost of the aggregate payload — relevant for an 'everything' tool.

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 lines with the core idea front-loaded and the prerequisite clearly separated. There is minor marketing flavor in 'Everything ... in a single call', but no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an aggregate read tool with no output schema, so the description is the only place an agent could learn what a 'passport' returns — versions, provenance, materials, print history, or all of them. That crucial content is entirely absent, leaving the agent unable to judge whether the call satisfies its need.

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?

Only one parameter exists and schema coverage is 100%, with the schema explaining that design_id is the slug under ~/.kiln/designs shared with the Versions and Models surfaces. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this is an aggregate fetch of all information about a single part/design, and the 'Part Passport' label gives it a memorable identity. However, there is no concrete verb and no statement of what 'everything' actually contains, so an agent cannot distinguish it from siblings like get_design, inspect_design, design_session, or model_details without guessing.

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 only guidance is the prerequisite 'Needs Kiln Pro', which is a gating condition rather than usage context. There is no statement of when to reach for this instead of the many sibling read tools that also return design information, and no exclusion criteria.

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