The Quartermaster

Is this worth it?

quartermaster_check_piece

Read-onlyIdempotent

Judge one piece of menswear before someone pays for it. Use when someone asks whether a piece of men's clothing or a pair of men's shoes is worth it ("is this worth it?", "is this a good deal?", "should I buy this?"), or pastes a men's clothing or shoe listing with a price, including Nordstrom Rack, outlet, eBay and Grailed finds. Give the maker, the category and the price, plus where it is sold and, if known, the compare-at price, fiber and build from the listing. Returns a verdict (Worth it, Worth it if the tag checks out, Only at a lower price, Skip it, Pay less, or Not enough to judge when the ledger does not grade the maker for that category and the listing gives no fiber or build that the ledger can score), the maker's grade, the fair price band for that kind of seller, what to check on the tag, cost per wear, and graded makers in the same category (same grade or better when the maker is graded). Limits: menswear only; prices are US dollars from the QuarterMaster ledger of 53 makers, checked September 2026, not live store prices; no stock, size or delivery checks; no orders.

Input Schema

Name	Required	Description
`build`	No	Shoe or jacket construction, if the listing says.
`fiber`	No	Fiber content from the listing, e.g. "100% wool" or "55% polyester".
`maker`	No	Brand or maker name as written on the listing, e.g. "Allen Edmonds", "Levi's", "J.Crew".
`price`	Yes	Price being asked, in US dollars.
`where`	No	full (brand site or department store), offprice (Nordstrom Rack, TJ Maxx, Marshalls), outlet (brand outlet or factory store), grey (marketplace seller), resale (eBay, Grailed, consignment). Default full.
`category`	Yes	One of: shoes (Leather shoes), boots (Boots), sneakers (Sneakers), tailoring (Suits, jackets, trousers), shirts (Shirts), knitwear (Knitwear), outerwear (Outerwear), watches (Watches), denim (Jeans), tees (Tees and polos), chore (Chore jackets and overshirts), chinos (Chinos and cotton trousers).
`compare_at`	No	The "compare at" or original price on the tag, if shown.

Output Schema

Name	Required	Description	Default
`grade`	Yes
`maker`	Yes
`price`	Yes
`where`	Yes
`dossier`	Yes
`reasons`	Yes
`verdict`	Yes
`category`	Yes
`fair_band`	Yes
`in_ledger`	Yes
`better_value`	Yes
`cost_per_wear`	Yes
`lifespan_years`	Yes
`estimated_wears`	Yes
`check_on_the_tag`	Yes
`maker_not_found_suggestions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / verdict / enum

Added value: +[
+  "Worth it",
+  "Worth it if the tag checks out",
+  "Only at a lower price",
+  "Skip it",
+  "Pay less",
+  "Not enough to judge"
+]

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "better_value": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "dossier": {
+            "type": "string"
+          },
+          "grade": {
+            "enum": [
+              "S",
+              "A",
+              "B",
+              "C",
+              "D"
+            ],
+            "type": "string"
+          },
+          "maker": {
+            "type": "string"
+          },
+          "usual_high": {
+            "type": "number"
+          },
+          "usual_low": {
+            "type": "number"
+          },
+          "where": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "maker",
+          "grade",
+          "usual_low",
+          "usual_high",
+          "where",
+          "dossier"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "category": {
+      "type": "string"
+    },
+    "check_on_the_tag": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "cost_per_wear": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "dossier": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "estimated_wears": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "fair_band": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "high": {
+              "type": "number"
+            },
+            "low": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "low",
+            "high"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "grade": {
+      "anyOf": [
+        {
+          "enum": [
+            "S",
+            "A",
+            "B",
+            "C",
+            "D"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "in_ledger": {
+      "type": "boolean"
+    },
+    "lifespan_years": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "maker": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "maker_not_found_suggestions": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "price": {
+      "type": "number"
+    },
+    "reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "verdict": {
+      "type": "string"
+    },
+    "where": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "verdict",
+    "maker",
+    "in_ledger",
+    "maker_not_found_suggestions",
+    "grade",
+    "category",
+    "price",
+    "where",
+    "fair_band",
+    "reasons",
+    "check_on_the_tag",
+    "cost_per_wear",
+    "estimated_wears",
+    "lifespan_years",
+    "better_value",
+    "dossier"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent and closed-world traits, yet the description adds substantially more: the exact verdict vocabulary, the ledger's limitations (53 makers, snapshot checked September 2026, not live store prices), the US-dollar assumption, and an explicit 'no orders / no stock checks' boundary. This is rich behavioral context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and triggers are front-loaded, which is good, but the middle is a single sprawling sentence with a long parenthetical enumerating every verdict string, including an awkward nested clause. Since an output schema already exists, that return-value enumeration is largely redundant and weighs the description down.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter, closed-world scoring tool with an output schema, the description supplies everything an agent needs: trigger conditions, required inputs, verdict semantics, data-freshness limits, and explicit exclusions. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by framing which inputs drive the verdict — it explains that fiber and build are what the ledger scores, and that a missing maker grade plus no fiber/build yields the 'Not enough to judge' outcome. That causal link is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Judge one piece of menswear before someone pays for it') with unambiguous scope, and it is instantly distinguishable from sibling tools like quartermaster_get_maker, quartermaster_list_makers and quartermaster_plan_outfit. An agent can route to it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit trigger conditions with quoted user phrasings ('is this worth it?', 'should I buy this?') and names the input scenarios (pasted listings from Nordstrom Rack, outlet, eBay, Grailed). The menswear-only limit and the 'no stock, size or delivery checks' exclusion further bound when the tool applies.

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

All The Quartermaster tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?