Skip to main content
Glama

Add colors to a material

add_material_colors

Add the colors (filaments) you stock for one of your materials, each with a name, a hex color and a finish. 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": {
      "material_id": "<material_id>",
      "colors": "<colors>"
    },
    "name": "add_material_colors"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYes
material_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, non-idempotent write with no open-world access, so the description does not need to restate the safety profile. It does add a genuine requirement the annotations lack: a connected Printlooper account. It does not disclose whether colors are appended or replace existing ones, how duplicates are handled, or what the server returns on partial failure.

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?

Two short sentences, front-loaded with the action and resource, followed by the prerequisite. No filler and nothing buried.

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 two-parameter write with a nested array of up to 50 entries and no output schema, the description covers the core purpose and auth prerequisite but leaves meaningful gaps: append-vs-replace semantics, duplicate handling, and the constraint/enum details that the undocumented schema does not convey in prose.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the burden and only partly meets it: it explains that each colors entry has a name, hex and finish, and translates "colors" into domain terms (filaments). It says nothing about material_id, the 1-50 array bounds, the finish enum values (matte/glossy/smooth/textured/silk), or the hex pattern, all of which an agent must read from the raw schema.

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 names a specific verb and resource ("Add the colors (filaments)") scoped to "one of your materials", and clarifies that a color bundle includes name, hex and finish. It implicitly separates itself from add_material by being about colors on an existing material, but never says so explicitly, so it falls short of full sibling differentiation.

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?

Usable context is implied: this is for stocking colors against a material you already have, and a connected Printlooper account is a stated prerequisite. There is no explicit when-not guidance, no mention of what to do if the material already has colors, and no pointer to an alternative tool such as add_material.

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