Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_best_material_substitute

Read-only

Returns the single top-ranked alternative filament for a given material like PLA or PETG, giving a quick substitute pick for 3D printing.

Instructions

Get the single best substitute for a filament material (quick shortcut).

Returns one top-ranked alternative. For a full ranked list with trade-off
details and filtering, use ``find_material_substitute`` instead.

Args:
    material: The original filament material (e.g. "PLA", "PETG").

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_best_material_substitute"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesThe original filament material (e.g. "PLA", "PETG").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"The original filament material (e.g. \"PLA\", \"PETG\")."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/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. The description adds genuine value by stating the result is a single top-ranked pick rather than a list, but it does not disclose the ranking basis or what happens when no suitable substitute exists. That is a meaningful but modest increment over the annotations.

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 purpose and the sibling routing are front-loaded in the first two sentences, which is exactly the right order. The trailing Args block merely restates the input schema and is redundant, keeping this from a 5.

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 one-parameter, side-effect-free lookup with no output schema, the description covers purpose, the alternative, and output cardinality. It omits the no-match/empty-result case and any hint about how 'best' is determined, which are the remaining gaps an agent would want before relying on it.

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% with a single required 'material' parameter, and the description's Args section repeats the schema wording verbatim. It adds no format, casing, or accepted-value constraints beyond the schema's own examples ('PLA', 'PETG'), so the baseline of 3 applies.

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?

States a specific verb and resource: 'Returns the single best substitute material for a given filament material.' It immediately names the sibling it differs from ('find_material_substitute') and characterizes this tool as the 'convenience shortcut,' so an agent can place it correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this when you just need one quick answer, use find_material_substitute when you need the full ranked list with tradeoffs. Both the when and the alternative are named directly rather than 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