Skip to main content
Glama

Add a material

add_material

Add a material your shop prints (PLA, PETG, ABS, TPU, ASA, RESIN or NYLON) with its prices. Then add colors with add_material_colors. Needs a connected Printlooper account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "price_per_gram_usd": "<price_per_gram_usd>"
    },
    "name": "add_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
setup_fee_usdNo
default_finishNoLeft out, the material starts on matte, or on its first allowed finish where it has no matte (PETG)
lead_time_daysNo
min_job_price_usdNo
price_per_gram_usdYes
failure_rate_percentNo
post_processing_fee_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / default_finish / default
      Removed value: -"matte"
    • addedInput schema / properties / default_finish / description
      Added value: +"Left out, the material starts on matte, or on its first allowed finish where it has no matte (PETG)"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-reversible-duplicate profile is partly covered. The description adds real value beyond that by disclosing the authentication prerequisite and the required follow-up tool. It never explains what happens when the same material is added twice, which is the main remaining gap given idempotentHint=false.

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?

Three short sentences, front-loaded with the action and the allowed types before the prerequisite and follow-up. Nothing is padded, though the type enumeration partially duplicates the schema enum.

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?

For a non-idempotent write tool with 8 parameters, no output schema and very low schema coverage, the description covers auth and sequencing but says nothing about pricing semantics, defaults, or duplicate handling. It is adequate to start the call but not to make an informed one.

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

Parameters2/5

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

Schema description coverage is only 13% across 8 parameters, so the description is expected to compensate and largely does not. It only conveys that the material is added 'with its prices', leaving setup_fee_usd, lead_time_days, min_job_price_usd, failure_rate_percent and post_processing_fee_usd with no explanation of units, effect, or defaults anywhere.

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 ('Add a material your shop prints') and even enumerates the seven supported material types, so the agent knows exactly what is being created. It does not explicitly contrast with set_material_prices or import_catalog, but the creation framing is distinct enough to act on.

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?

Gives two concrete usage signals: an account prerequisite ('Needs a connected Printlooper account') and an explicit follow-up step ('Then add colors with add_material_colors'), which correctly routes the agent within a known two-step workflow. It stops short of stating when not to use it, e.g. when the material already exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources