The Quartermaster

Start a fitting

quartermaster_start_fitting

Read-onlyIdempotent

Start a guided menswear fitting with QuarterMaster. Use when someone asks what a man should wear or buy for an occasion: "what should I wear to my friend's wedding", a work dinner, a first date, a rainy weekend away, coffee with friends, or "I have nothing to wear". Returns the tailor's questions in order, the occasions it dresses for, and the full kit each impression calls for, so the person can compare. The answers are the inputs to quartermaster_plan_outfit. 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	Default
`room`	No	Optional. The occasion, if already known.

Output Schema

Name	Required	Description	Default
`host`	Yes
`rooms`	Yes
`questions`	Yes
`how_to_run_it`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "host": {
+      "type": "string"
+    },
+    "how_to_run_it": {
+      "type": "string"
+    },
+    "questions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "ask": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "note": {
+            "type": "string"
+          },
+          "only_if": {
+            "type": "string"
+          },
+          "options": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "title"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "suggestions": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "ask"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rooms": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "impressions": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "kit": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "title",
+                "kit"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "note": {
+            "type": "string"
+          },
+          "photo": {
+            "type": "string"
+          },
+          "pieces_you_might_own": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "label": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "label"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "note",
+          "photo",
+          "impressions",
+          "pieces_you_might_own"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "host",
+    "how_to_run_it",
+    "rooms",
+    "questions"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: prices come from a static ledger of 53 makers checked September 2026 and are not live store prices, and there are no stock, size, delivery or ordering capabilities. The 'returns the tailor's questions...' sentence partly restates what the output schema already provides.

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?

Front-loaded with purpose then usage, then limits, so an agent gets the essentials immediately. The long list of example utterances overlaps with the enum values in the schema and could be trimmed without losing meaning.

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?

Covers purpose, triggering situations, workflow hand-off to quartermaster_plan_outfit, domain scope, data provenance and explicit capability exclusions, and an output schema exists for return details. An agent has everything needed to select and call it correctly.

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 coverage is 100% and the single 'room' parameter is fully documented with its enum, so the schema does the heavy lifting. The description's occasion examples loosely mirror the enum values but add no format or selection guidance beyond 'Optional. The occasion, if already known.'

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?

States a specific verb and resource ('Start a guided menswear fitting with QuarterMaster') and makes the domain boundary (menswear styling, not shopping) clear, which separates it from quartermaster_list_makers, quartermaster_get_maker and quartermaster_check_piece. The reference to quartermaster_plan_outfit pins its place in the workflow.

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?

Explicitly states when to use it ('Use when someone asks what a man should wear or buy for an occasion') with concrete trigger utterances, and names the downstream tool whose inputs these answers become. It also states when not to rely on it (no stock, size or delivery checks; no orders).

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?