Skip to main content
Glama

suggest_material_for_order

Recommends the best material and technology for ordering a 3D print from a fulfillment provider based on use case, budget, and requirements like weather resistance or food safety.

Instructions

Suggest a material when ordering a print from a fulfillment provider.

        Use this when routing a print job to a service (Sculpteo, Craftcloud)
        and need to pick the right material + technology for the order.

        **Which material tool to use:**

        - Ordering a print from a service? → ``suggest_material_for_order`` (this tool)
        - Designing a part and need engineering specs? → ``recommend_design_material``
        - Quick intent-based pick for your own printer? → ``recommend_material``

        Args:
            use_case: What the part is for. Options: decorative, functional,
                mechanical, prototype, miniature, jewelry, enclosure, wearable,
                outdoor, food_safe.
            budget: Price preference: "budget", "mid", or "premium". Empty = any.
            need_weather_resistant: Only recommend weather-resistant materials.
            need_food_safe: Only recommend food-safe materials.
            need_high_detail: Prefer high-detail materials (SLA/MJF).
            need_high_strength: Prefer high-strength materials (SLS/MJF).

        Returns ranked material recommendations with technology, reasoning,
        price tier, and which fulfillment provider to use.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNo
use_caseYes
need_food_safeNo
need_high_detailNo
need_high_strengthNo
need_weather_resistantNo
Behavior4/5

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

Annotations are absent, so the description carries full burden. It discloses that the tool returns 'ranked material recommendations with technology, reasoning, price tier, and which fulfillment provider to use.' It does not mention any side effects or destructive actions, which is consistent with a suggestion tool. However, it could explicitly state that no state changes occur, but the description is sufficient for safe use.

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 clear one-sentence summary, a usage paragraph, a bullet list for tool alternatives, and a bullet list for parameters. Every sentence is informative and earns its place, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, 1 required, no output schema), the description is complete. It explains when to use, each parameter's role, the return format, and distinguishes from siblings. An agent has all necessary information to invoke it correctly.

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 description coverage is 0%, but the description independently lists all 6 parameters with clear explanations (e.g., 'use_case: What the part is for...' and boolean flags like 'need_weather_resistant: Only recommend weather-resistant materials.'). This adds significant meaning beyond the schema's bare names 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 the tool's purpose: 'Suggest a material when ordering a print from a fulfillment provider.' It uses a specific verb (suggest) and resource (material for order). Additionally, it distinguishes itself from sibling tools by providing a comparison table explicitly naming 'recommend_design_material' and 'recommend_material' with their contexts.

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?

The description explicitly states when to use this tool: 'Use this when routing a print job to a service (Sculpteo, Craftcloud) and need to pick the right material + technology for the order.' It also provides clear when-not/alternatives via the bullet list under 'Which material tool to use,' making the decision straightforward for an agent.

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