Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_orientation

Read-only

Check a 3D model's print orientation for stability by analyzing its height-to-base ratio; warns about wobble or mid-print failure and suggests reorientation if needed.

Instructions

Check if a model's orientation is stable for printing.

Analyzes the height-to-base ratio and warns if the model is likely to
wobble or fail mid-print.  Suggests reorientation if needed.

:param model_path: Path to the STL or OBJ model file.
:returns: Dict with stability assessment.

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": {
      "model_path": "<model_path>"
    },
    "name": "check_orientation"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYesPath to the STL or OBJ model file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / model_path / description
      Added value: +"Path to the STL or OBJ model file."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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. Beyond that, the description discloses the actual heuristic (height-to-base ratio) and what the agent will get back conceptually — a stability assessment, a warning condition, and a reorientation suggestion. It stops short of describing thresholds or the dict's keys, but the added context is real.

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 purpose is front-loaded in the first sentence, followed by a tight explanation of what is analyzed and what happens on failure. The trailing ':param' and ':returns' lines are docstring artifacts that duplicate the schema and slightly dilute the otherwise efficient prose.

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-parameter read-only diagnostic with no output schema, the description covers what is measured, the failure mode detected, and the corrective suggestion. It is largely complete; only the shape of the returned assessment and any actionable threshold remain unstated.

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?

With one parameter and 100% schema description coverage, the baseline is 3. The description's ':param model_path: Path to the STL or OBJ model file.' is a verbatim restatement of the schema entry, adding no new meaning such as supported variants, path resolution, or file-size expectations.

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 ('check if a model's orientation is stable for printing') plus the method used (height-to-base ratio) and the outcome (warn on wobble, suggest reorientation). It does not distinguish itself from related siblings like optimize_print_orientation or analyze_printability, so an agent must infer that this one only diagnoses rather than fixes.

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?

Usage is implied by 'suggests reorientation if needed' and 'likely to wobble or fail mid-print', which hints at a pre-print sanity check. There is no explicit when-to-use statement, no mention of the natural follow-up tool (optimize_print_orientation / auto_orient_model), and no exclusions.

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