Skip to main content
Glama

Little Works

quote_materials_cart

Quote a multi-SKU materials cart with quantities and bulk discounts. Digitized transaction preview before PO.

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": {
      "lines": "<lines>"
    },
    "name": "quote_materials_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoJob / problem label
linesYesCart lines: [{sku, quantity}]
placeNoJobsite city, e.g. victoria-bc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. 'Quote' and 'preview' usefully signal that this is non-committal pricing rather than an order, which is the key behavioral distinction. It says nothing about whether quotes expire, whether bulk discounts are guaranteed at order time, or what permissions are needed.

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 short sentences, front-loaded with the action and resource. 'Digitized transaction preview' is slightly jargon-heavy phrasing where 'price preview' would be plainer, but nothing is wasted.

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?

There is no output schema and no annotations, so the description is the only source of shape information. It never says what a quote returns (line pricing, discount tiers, totals, validity), which is exactly the information an agent needs to know this tool succeeded.

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 100%, so the baseline is 3. The description reinforces the 'lines' semantics (multi-SKU, quantities) and hints that quantity drives bulk-discount tiers, but adds no meaning for the 'job' or 'place' parameters beyond what the schema already documents.

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 ('Quote') and resource ('multi-SKU materials cart') plus two distinguishing traits: quantities with bulk discounts, and that it is a preview before a PO. That separates it from a committing sibling like draft_materials_order or buy_material, though it never names the contrast explicitly.

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?

'Digitized transaction preview before PO' implies the moment of use (pre-purchase pricing check), which is real contextual guidance. There is no explicit when-not guidance, no stated prerequisite (e.g., a job or place must exist first), and no named alternative for actually placing the order.

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