Skip to main content
Glama

What a job would cost at my prices

estimate_job_price
Read-onlyIdempotent

What your shop would charge for a print of a given weight in one of your materials, with the breakdown, for one unit or a batch. 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>",
      "weight_grams": "<weight_grams>"
    },
    "name": "estimate_job_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNo
material_idYes
weight_gramsYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: an account-connection prerequisite and the fact that the result includes a cost breakdown and scales from one unit to a batch. It does not state whether unpriced materials error or what the breakdown fields are.

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?

Two sentences, front-loaded with the core purpose and followed by the prerequisite. No filler; the only slight slack is the trailing 'for one unit or a batch', which could be tighter but does convey batch support.

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 simple three-parameter read tool with no output schema, the definition covers purpose, prerequisite and batch behavior, which is close to sufficient. The remaining gap is the lack of any hint about where material_id values come from and how the returned breakdown is shaped, both of which an agent must guess.

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 must carry the load, and it does partially: weight maps to 'a given weight', material_id to 'one of your materials', and quantity to 'one unit or a batch'. It omits how to obtain a valid material_id (presumably list_materials), and says nothing about the 0.1–20000 g or 1–10000 unit bounds.

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 (charge/estimate) and resource (price for a print of a given weight in one of your materials), plus the scope of returning a breakdown for single units or batches. The phrase 'your shop' / 'at my prices' implicitly separates it from market-level pricing siblings such as get_pricing_benchmarks, but no sibling is named outright.

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?

Usage is only implied: an agent can infer this is the tool to call when it wants a quote rather than to change prices, and the 'Needs a connected Printlooper account' sentence states a prerequisite. There is no explicit when-to-use versus when-not guidance, and no pointer to set_material_prices (to change prices) or get_pricing_benchmarks (to compare against the market).

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