Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

intake_engineering_drawing

Registers an engineering drawing or related design file and retrieves its pages for reading, enabling structured intake and page-by-page review before assessment.

Instructions

Start a drawing intake: register the drawing and get its pages to read.

Needs Kiln Business.

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": {
      "file_path": "<file_path>"
    },
    "name": "intake_engineering_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoOptional default material for later assessment (e.g. "PETG-CF"); can be overridden per assessment call. Default: "".
file_pathYesPath to the drawing (.pdf/.png/.jpg), slide deck (.pptx/.ppt), or CAD (.step/.stp) file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the drawing (.pdf/.png/.jpg), slide deck (.pptx/.ppt), or CAD (.step/.stp) file."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"\"."New value: +"Optional default material for later assessment (e.g. \"PETG-CF\"); can be overridden per assessment call. Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so safety profile is covered. The description adds real context beyond that: the Kiln Business entitlement gate and the fact that the call yields pages to read. It stops short of covering idempotency, re-intake behavior, or side effects of registering a file.

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, front-loaded sentences with no filler; the action comes first and the prerequisite second. It could be one sentence tighter, but nothing is wasted.

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 two-parameter intake mutation with no output schema, the description omits what is returned (page handles/IDs?) and what the agent should do with the pages next. The entitlement note is helpful, but an agent still has to guess at the follow-up step in the pipeline.

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 both file_path and the optional material default are fully documented in the schema itself. The description adds nothing about parameter meaning, format, or supported extensions beyond what is already structured. 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 concrete verb plus resource ('start a drawing intake: register the drawing') and adds the immediate payoff ('get its pages to read'), so an agent understands this is the entry point of a drawing pipeline. It is distinguishable from downstream siblings such as assess_drawing_manufacturability and submit_drawing_extraction, though those are not named.

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?

'Start' implies first-in-sequence usage and 'Needs Kiln Business' gives a hard prerequisite, which is genuinely useful routing information. However, it never says when NOT to use it, nor names any sibling (e.g. submit_drawing_extraction, analyze_print_file, import_step_file) that an agent might confuse it with.

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