Skip to main content
Glama

recommend_adhesive

Read-only

Recommends and ranks adhesives for joining two printed plastics, with prep steps and a cure schedule tailored to the materials and service conditions.

Instructions

Which adhesive joins these two printed plastics — ranked, with prep + cure schedule.

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": {
      "material_a": "<material_a>"
    },
    "name": "recommend_adhesive"
  }
}

Input Schema

NameRequiredDescriptionDefault
flexibleNoTrue if the joint must flex (e.g. bonding TPU) -- limits to elastomeric adhesives. Default: false.
reusableNoTrue if the joint must come apart later -- the engine will tell you to use a screw/insert instead of glue. Default: false.
show_mathNoSurface source-free engineering detail -- measurements, public standards, confidence, test substrate, and service conditions. Off by default (plain English). Default: false.
material_aYesFirst printed material (e.g. "PLA", "PETG", "ABS", "Nylon", "TPU", "PP", "PETG-CF").
material_bNoSecond material. Omit to bond a material to itself. Default: "".
uv_exposureNoTrue if it sees sunlight (penalises UV-weak glues). Default: false.
food_contactNoTrue to require a food-contact-certified adhesive. A compliant glue does not make a printed part food-safe on its own. Default: false.
load_bearingNoTrue if the bond carries load -- adds an engineer-review flag (adhesive bonds on plastic are not a structural promise). Default: false.
biocompatibleNoTrue to require an ISO 10993 / USP Class VI biocompatible adhesive (medical-adjacent use). Default: false.
heat_availableNoTrue if you can warm the part (oven/dryer ~60°C) to heat-accelerate an epoxy's full cure. Default: false.
water_exposureNo"" (none), "humid", "splash", "submersion", or "constant". Default: "".
vacuum_outgassingNoTrue to require an ASTM E595 low-outgassing adhesive (vacuum, cleanroom or aerospace use). Default: false.
cure_time_availableNoHow fast you need it -- "any" (default), "instant" (<1 min), "fast" (<5 min), "medium" (<1 h), "slow". Default: "any".
temperature_exposureNoWhere it lives -- "indoor" (default), "outdoor", "outdoor_sun", "hot_car", "dishwasher", "near_heat", "boiling", "engine_bay". Sets the required service temperature. Default: "indoor".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.5.1
    • changedInput schema / properties / biocompatible / description
      Previous value: -"Default: false."New value: +"True to require an ISO 10993 / USP Class VI biocompatible adhesive (medical-adjacent use). Default: false."
    • changedInput schema / properties / cure_time_available / description
      Previous value: -"Default: \"any\"."New value: +"How fast you need it -- \"any\" (default), \"instant\" (<1 min), \"fast\" (<5 min), \"medium\" (<1 h), \"slow\". Default: \"any\"."
    • changedInput schema / properties / flexible / description
      Previous value: -"Default: false."New value: +"True if the joint must flex (e.g. bonding TPU) -- limits to elastomeric adhesives. Default: false."
    • changedInput schema / properties / food_contact / description
      Previous value: -"Default: false."New value: +"True to require a food-contact-certified adhesive. A compliant glue does not make a printed part food-safe on its own. Default: false."
    • changedInput schema / properties / heat_available / description
      Previous value: -"Default: false."New value: +"True if you can warm the part (oven/dryer ~60°C) to heat-accelerate an epoxy's full cure. Default: false."
    • changedInput schema / properties / load_bearing / description
      Previous value: -"Default: false."New value: +"True if the bond carries load -- adds an engineer-review flag (adhesive bonds on plastic are not a structural promise). Default: false."
    • addedInput schema / properties / material_a / description
      Added value: +"First printed material (e.g. \"PLA\", \"PETG\", \"ABS\", \"Nylon\", \"TPU\", \"PP\", \"PETG-CF\")."
    • changedInput schema / properties / material_b / description
      Previous value: -"Default: \"\"."New value: +"Second material.  Omit to bond a material to itself. Default: \"\"."
    • changedInput schema / properties / reusable / description
      Previous value: -"Default: false."New value: +"True if the joint must come apart later -- the engine will tell you to use a screw/insert instead of glue. Default: false."
    • changedInput schema / properties / show_math / description
      Previous value: -"Default: false."New value: +"Surface source-free engineering detail -- measurements, public standards, confidence, test substrate, and service conditions. Off by default (plain English). Default: false."
    • changedInput schema / properties / temperature_exposure / description
      Previous value: -"Default: \"indoor\"."New value: +"Where it lives -- \"indoor\" (default), \"outdoor\", \"outdoor_sun\", \"hot_car\", \"dishwasher\", \"near_heat\", \"boiling\", \"engine_bay\".  Sets the required service temperature. Default: \"indoor\"."
    • changedInput schema / properties / uv_exposure / description
      Previous value: -"Default: false."New value: +"True if it sees sunlight (penalises UV-weak glues). Default: false."
    • changedInput schema / properties / vacuum_outgassing / description
      Previous value: -"Default: false."New value: +"True to require an ASTM E595 low-outgassing adhesive (vacuum, cleanroom or aerospace use). Default: false."
    • changedInput schema / properties / water_exposure / description
      Previous value: -"Default: \"\"."New value: +"\"\" (none), \"humid\", \"splash\", \"submersion\", or \"constant\". Default: \"\"."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: output is ranked with prep/cure schedule, and the tool is gated behind Kiln Pro. It does not cover rate limits or failure modes, so a 3 is fair.

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 sentences, front-loaded with the core question the tool answers, followed by the tier requirement. No wasted wording, though 'Needs Kiln Pro' is slightly cryptic without elaboration.

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 14-parameter tool with no output schema, the description usefully signals the return shape (ranked list with prep and cure schedule) and the tier gate. Combined with fully documented parameters and annotations, an agent has enough to call it correctly.

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 all 14 parameters carry rich descriptions (defaults, enums-in-prose, examples). The description adds no parameter meaning beyond the schema, so the 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 specific verb and resource: recommends which adhesive joins two printed plastics, and adds that results are ranked with prep and cure schedule. An agent can tell this apart from joint/hardware siblings, though it doesn't name an alternative explicitly.

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 only usage guidance is the prerequisite 'Needs Kiln Pro.' There is no explicit when-to-use vs when-not, and no pointer to related siblings like recommend_joint_strategy or get_joint_recommendation, so selection context is only implied.

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