Skip to main content
Glama

Change material prices

set_material_prices
Destructive

Change the prices of one of your materials (price per gram, minimum job, failure surcharge, setup and post-processing fees, lead time). New quotes use them right away. Show the user the change before making it. 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>"
    },
    "name": "set_material_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
material_idYes
setup_fee_usdNo
lead_time_daysNo
min_job_price_usdNo
price_per_gram_usdNoFor example 0.04 for 4 cents a gram
failure_rate_percentNo
post_processing_fee_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety bar is partly covered. The description adds real value beyond them: the change takes effect immediately for new quotes, a human confirmation is expected first, and an authenticated account is required. It still omits whether omitted fields are left untouched or reset.

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 with the core action front-loaded and no filler. The confirmation and account requirements are appended compactly, though the account prerequisite sits at the tail where it is easy to skim past.

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 destructive, non-idempotent mutation with seven parameters and thin schema documentation, the description covers effect timing and confirmation but not the critical partial-update question (only material_id is required, so do omitted prices stay as-is?) nor how to obtain a material_id. Adequate but with a clear gap on mutation semantics.

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 only 14% (just the price_per_gram_usd example), so the description carries weight — and it does map its field list onto most parameters (price per gram, minimum job, failure surcharge, setup and post-processing fees, lead time). However, it says nothing about material_id, about the nullable parameters, or about defaults for omitted fields, leaving partial-update semantics unexplained.

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 ('Change the prices of one of your materials') and enumerates the affected price components, so it is clearly not add_material or list_materials. It stops short of naming or contrasting a sibling explicitly, but the resource is unambiguous.

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 gives workflow-relevant conditions: 'New quotes use them right away', 'Show the user the change before making it', and 'Needs a connected Printlooper account'. These are prerequisites and a confirmation step rather than true when-to-use/when-not guidance against alternatives, so usage is only implied.

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