Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_post_processing_guide

Read-only

Retrieve bounded post-processing guidance for a 3D-printed material and selected goal, or get a compact compatibility overview when no goal is set.

Instructions

Get bounded public post-processing help for one goal.

        Pass ``surface_finish``, ``paint``, ``strengthen``, or the name of
        one listed technique. Omitting ``goal`` returns a compact
        compatibility overview rather than the complete guide.

        Args:
            material: Material ID (e.g. "pla", "abs", "petg", "nylon").
            goal: Optional: ``"surface_finish"``, ``"paint"``,
                ``"strengthen"``, or the name of one technique from the
                overview.  Omit for the compact overview.

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": {
      "material": "<material>"
    },
    "name": "get_post_processing_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoOptional: ``"surface_finish"``, ``"paint"``, ``"strengthen"``, or the name of one technique from the overview. Omit for the compact overview.
materialYesMaterial ID (e.g. "pla", "abs", "petg", "nylon").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / goal / description
      Added value: +"Optional: ``\"surface_finish\"``, ``\"paint\"``, ``\"strengthen\"``, or the name of one technique from the overview.  Omit for the compact overview."
    • addedInput schema / properties / material / description
      Added value: +"Material ID (e.g. \"pla\", \"abs\", \"petg\", \"nylon\")."
  2. Changed1 schema field changedv1.5.0
    • removedInput schema / properties / goal / default
      Removed value: -null
  3. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / goal
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Goal"
+}
  4. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive, and closed-world, so safety is covered. The description adds a genuine behavioral trait beyond them: the content is 'bounded' and 'public,' and omitting goal yields a compact compatibility overview rather than the complete guide. It stops short of describing result format, depth, or failure behavior for unknown materials/techniques.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and overview-behavior are front-loaded and useful, but the goal parameter is described twice — once in the body and again inside the Args block — which is pure duplication of the schema. Trimming the Args section would remove the only real waste.

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 two-parameter read-only lookup with annotations and no output schema, the description covers purpose, required input, optional mode, and the default behavior when the optional field is omitted. A brief note on what the guide contains or how unknown technique names are handled would close the remaining 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 repeats the schema text nearly verbatim for both material and goal, adding no new meaning such as accepted technique-name format, case sensitivity, or material-ID validation rules. Baseline 3 is the correct ceiling when the schema already carries all parameter semantics.

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 ('Get bounded public post-processing help') plus the scoping unit ('one goal'), so it is clearly a retrieval tool for post-processing guidance rather than a slicing or material-property tool. It does not name any sibling or contrast itself with adjacent lookups like get_material_design_profile, so sibling differentiation is only implied by the 'post-processing' subject.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly tells the agent how to select modes: pass a category or a listed technique name, or omit goal for the compact overview. That is clear caller-facing context, but there are no exclusions (e.g., when to prefer a full guide or another tool) and no prerequisites such as needing a valid material ID first.

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