Skip to main content
Glama

recommend_adhesion_settings

Analyzes a 3D model's geometry and material to recommend brim width and raft settings, considering warp risk and printer type.

Instructions

Recommend brim/raft settings for a 3D model based on geometry + material.

        Analyzes the model's bed contact area, material warp tendency, and
        printer type to produce a concrete brim width and optional raft
        recommendation.  Returns ``slicer_overrides`` ready to pass to
        ``slice_model`` or ``slice_and_print``.

        Args:
            model_path: Path to an STL or OBJ mesh file.
            material: Filament material (e.g. ``"PLA"``, ``"ABS"``,
                ``"PETG"``).  Affects warp risk calculation.
            printer_id: Optional printer model ID (e.g. ``"bambu_a1"``).
                Used to detect bed-slinger printers that need wider brims.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialNoPLA
model_pathYes
printer_idNo
Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes the analysis process and output format (slicer_overrides) but does not explicitly state that the tool is read-only or disclose any side effects (e.g., file modifications, permissions, rate limits). It is adequate but could be more transparent.

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

Conciseness5/5

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

The description is well-structured with a concise summary followed by clear parameter bullet points. Every sentence contributes to understanding the tool's purpose, inputs, and output. No wasted words.

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?

The tool has no output schema, but the description explains the return value (slicer_overrides) and its usage. It covers main aspects but lacks details on edge cases (e.g., no bed contact) or error conditions. Still, it is sufficiently complete for its intended use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description provides full semantic meaning for each parameter: model_path (STL/OBJ), material (affects warp risk, defaults to PLA), and printer_id (for bed-slinger detection, optional). It adds significant value beyond the schema's basic titles and types.

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

Purpose5/5

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

The description clearly states it recommends brim/raft settings based on geometry and material, specifying analysis inputs (bed contact area, warp tendency, printer type) and output (brim width, raft, slicer_overrides). It distinguishes from siblings like analyze_warping_risk and recommend_settings by being specific about its output and usage with slice_model.

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 description implies usage when needing brim/raft settings but does not explicitly state when to use or when not to use, nor does it mention alternatives or exclusions. Among siblings, there are related tools like recommend_settings and analyze_warping_risk, but no guidance on selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server