Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

check_material_sufficiency

Check if a printer has enough material for a print job and get actionable suggestions when material is insufficient, including shelf spool availability and purchase links.

Instructions

Check if a printer has enough material for a print job.

        When material is insufficient, generates actionable suggestions
        including shelf spool availability, pause-and-swap hints, and
        purchase links.  Suggestions that point at OTHER machines are a
        fleet-wide answer and need Kiln Business; the check itself —
        does THIS printer have enough — works on every tier.

        Args:
            printer_name: Name of the printer to check.
            required_grams: Amount of material needed in grams.
            material_type: Optional material type filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
printer_nameYes
material_typeNo
required_gramsYes

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of transparency. It discloses that insufficient material triggers suggestions, but does not clarify if the check is read-only, the output format, or edge cases. Moderate transparency, but incomplete.

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 concise and well-structured: purpose first, then behavior details, then parameter list. It avoids unnecessary fluff but could integrate the tier limitation more smoothly.

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 no output schema and no annotations, the description covers core functionality and suggestions, but lacks details on output format, edge cases, and behavior when material is sufficient. More context needed for an agent to use it effectively.

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?

Since schema has 0% description coverage, the description compensates by listing each parameter with a brief explanation. This adds meaning beyond types and required status, though more detail on formats or allowed values would improve clarity.

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 checks if a printer has enough material for a print job, with a specific verb and resource. It distinguishes itself from siblings by emphasizing that this check is for a single printer and works on every tier, while fleet-wide suggestions require a different tool.

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?

The description provides context on when to use the tool (checking a specific printer's sufficiency) and notes that fleet-wide suggestions need Kiln Business. However, it does not explicitly name alternative tools for fleet-wide checks, leaving some guidance gaps.

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