Skip to main content
Glama

get_material_design_profile

Retrieve comprehensive engineering properties for 3D printing materials, including mechanical strength, thermal limits, and design constraints, to inform part design and material selection.

Instructions

Get full engineering properties for a 3D printing material.

        Returns mechanical properties (tensile/flexural strength, impact
        resistance, creep behavior), thermal limits (glass transition,
        max service temp), chemical properties (UV/moisture resistance,
        food safety), dimensional design limits (min wall thickness,
        max overhang, snap-fit tolerances), use-case ratings, and
        expert guidance notes.

        Use this to understand a specific material deeply — what it's
        good at, what it's bad at, and what design limits to respect.

        Args:
            material: Material ID — one of: pla, petg, abs, tpu, asa,
                nylon, polycarbonate.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
materialYes
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes the output content but does not explicitly state that the operation is read-only or non-destructive. It also lacks information on authentication requirements, rate limits, or side effects.

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 description is well-structured with bullet-like enumeration of property categories and a clear usage directive. It is slightly verbose but every sentence adds value. The key information is front-loaded.

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?

Given the lack of output schema and low schema coverage, the description provides a good high-level overview of the returned property categories. However, it does not specify the exact fields, return format, or structure, which would aid an agent in understanding the output.

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

Parameters4/5

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

The single parameter 'material' has 0% schema description coverage. The description compensates by enumerating the valid material IDs: pla, petg, abs, tpu, asa, nylon, polycarbonate. This provides clear semantic guidance beyond the schema's type and title.

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?

The description clearly states the tool returns 'full engineering properties' for a 3D printing material, listing specific property categories. However, it does not explicitly differentiate from sibling tools like get_material_properties or get_material_info, which may have overlapping purposes.

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 advises using this tool to 'understand a specific material deeply,' implying a comprehensive analysis. However, it does not provide guidance on when not to use it or mention alternatives like search or compare tools among the many material-related siblings.

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