Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

fulfillment_materials

Read-only

List and filter materials from external manufacturing services by name or technology to find IDs, colors, finishes, and pricing for quotes.

Instructions

List available materials from external manufacturing services.

        Returns materials with technology (FDM, SLA, SLS, etc.), color,
        finish, and pricing.  Use the material ``id`` when requesting a quote
        with ``fulfillment_quote``.

        The full catalog contains 2000+ materials.  Use the optional filter
        parameters to narrow results so agents can find the right material
        without overwhelming context windows.

        Args:
            search: Filter materials whose name contains this term
                (word-boundary match, case-insensitive).  E.g. ``"nylon"``
                matches "Nylon 12" and "Glass-filled Nylon" but not
                "Carbonylon".
            technology: Filter by manufacturing technology (word-boundary
                match, case-insensitive).  Common values: ``"SLS"``,
                ``"FDM"``, ``"SLA"``, ``"MJF"``, ``"DMLS"``.  Matches
                against both the technology field and the material name.
            limit: Maximum number of materials to return (default 50).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fulfillment_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of materials to return (default 50). Default: 50.
searchNoFilter materials whose name contains this term (word-boundary match, case-insensitive). E.g. ``"nylon"`` matches "Nylon 12" and "Glass-filled Nylon" but not "Carbonylon".
technologyNoFilter by manufacturing technology (word-boundary match, case-insensitive). Common values: ``"SLS"``, ``"FDM"``, ``"SLA"``, ``"MJF"``, ``"DMLS"``. Matches against both the technology field and the material name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Maximum number of materials to return (default 50). Default: 50."
    • addedInput schema / properties / search / description
      Added value: +"Filter materials whose name contains this term (word-boundary match, case-insensitive).  E.g. ``\"nylon\"`` matches \"Nylon 12\" and \"Glass-filled Nylon\" but not \"Carbonylon\"."
    • addedInput schema / properties / technology / description
      Added value: +"Filter by manufacturing technology (word-boundary match, case-insensitive).  Common values: ``\"SLS\"``, ``\"FDM\"``, ``\"SLA\"``, ``\"MJF\"``, ``\"DMLS\"``.  Matches against both the technology field and the material name."
  2. Changed4 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -50
    • addedInput schema / properties / limit / description
      Added value: +"Default: 50."
    • removedInput schema / properties / search / default
      Removed value: -null
    • removedInput schema / properties / technology / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds genuine value beyond them: it discloses the return fields (technology, color, finish, pricing), the catalog size (2000+), and the default limit of 50 with the context-window rationale. Only the lack of pagination/cursor behavior keeps it below a 5.

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?

Front-loaded with the purpose, then the return shape, then the workflow link to fulfillment_quote, then the filter rationale. The trailing Args section largely duplicates the schema and could be trimmed, but it is well organized and easy to scan.

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?

With no output schema, the description carries the burden of describing returned fields and does so (technology, color, finish, pricing). For a three-optional-parameter read tool with full annotation and schema coverage, nothing essential for correct invocation is missing.

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 Args block in the description restates the same word-boundary/case-insensitive matching rules and examples already present in the schema. It reinforces which parameters matter but adds no meaning beyond the structured data, 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: 'List available materials from external manufacturing services', and names the downstream consumer (fulfillment_quote). It does not distinguish itself from the many sibling list_* material tools (list_materials, list_available_materials, list_supported_materials, list_design_materials), so an agent may not know which catalog is authoritative without inspecting schemas.

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?

Clear guidance: the full catalog is 2000+ entries, so use the optional filters to avoid blowing the context window, and carry the returned material `id` into fulfillment_quote. It gives a clear use context but no explicit exclusions against sibling material-listing tools.

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