Skip to main content
Glama

find_printers_with_material

Locate 3D printers loaded with a specific material, sorted by remaining stock. Optionally filter by color and minimum grams.

Instructions

Find printers that have a specific material loaded.

        Returns printers with the matching material, sorted by
        remaining stock (most first).  Optionally filter by colour
        and minimum remaining grams.

        Args:
            material_type: Material type to find (e.g. ``"PLA"``).
            color: Optional colour filter.
            min_grams: Minimum remaining grams (default 0).
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo
min_gramsNo
material_typeYes
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that results are sorted by remaining stock and that optional filters exist, but does not address edge cases (e.g., no matching printers) or error conditions. Adequate but not exhaustive.

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 concise with a one-sentence summary followed by a clear parameter list. Every sentence adds value, no fluff. Well-structured for quick comprehension.

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?

The description explains the output ordering and filtering but does not specify the exact return format (e.g., printer IDs, names). Without an output schema, this missing detail reduces completeness for an agent that needs to parse results.

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?

The description adds complete parameter documentation, including example values ('PLA'), optional filters (color), and default behavior (min_grams default 0). Since the schema lacks descriptions, this fully compensates and adds significant meaning.

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 finds printers with a specific material loaded, using a specific verb and resource. It distinguishes from siblings like 'find_material_match' and 'list_trusted_printers' by focusing on printer availability by material.

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 implies usage (to find printers with a material) but provides no explicit guidance on when to use this tool versus alternatives like 'discover_printers' or 'printer_status'. No exclusions or prerequisites are mentioned.

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