MyHairMail Agent Tools

Get restock week for a colour

get_restock_eta

Read-onlyIdempotent

Expected back-in-stock week for one colour of a MyHairMail wig that is backordered or out of stock, from live factory availability. restock_eta_week is the Monday (YYYY-MM-DD) of the ISO week of expected arrival; eta_display is human phrasing ('week of Nov 9'). preorder_available=true means it can be ordered now and ships when restocked (for availability=preorder: the new style is open for pre-orders; false means not open yet). discontinued means it will not restock; the response then includes next_step naming the tool that finds an equivalent. For an in_stock colour this confirms availability; available_quantity gives the units available now. Terms: https://mcp.myhairmailtools.com/terms

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": {
      "brand": "<brand>",
      "style": "<style>",
      "color": "<color>"
    },
    "name": "get_restock_eta"
  }
}

Input Schema

Name	Required	Description
`brand`	Yes	Brand name, e.g. 'Envy', 'Jon Renau'
`color`	Yes	Colour name or code exactly as listed on the product, e.g. 'Prosecco' or 'FS26/31S6'
`style`	Yes	Style name, e.g. 'Charlotte Hand-Tied'

Output Schema

Name	Required	Description	Default
`note`	No
`match`	Yes
`product`	No
`retailer`	Yes
`next_step`	No
`did_you_mean`	No
`supported_brands`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedOutput schema / properties / product / properties / availability / enum

Previous value: -[
-  "in_stock",
-  "out_of_stock",
-  "backordered",
-  "discontinued"
-]New value: +[
+  "in_stock",
+  "out_of_stock",
+  "backordered",
+  "discontinued",
+  "preorder"
+]

Changed1 schema field changedOct 11, 2026
- addedOutput schema / properties / product / properties / available_quantity
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / color / description

Previous value: -"Colour name or code exactly as listed by check_stock, e.g. 'Prosecco' or 'FS26/31S6'"New value: +"Colour name or code exactly as listed on the product, e.g. 'Prosecco' or 'FS26/31S6'"

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / brand / description

Added value: +"Brand name, e.g. 'Envy', 'Jon Renau'"

addedInput schema / properties / color / description

Added value: +"Colour name or code exactly as listed by check_stock, e.g. 'Prosecco' or 'FS26/31S6'"

addedInput schema / properties / style / description

Added value: +"Style name, e.g. 'Charlotte Hand-Tied'"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "did_you_mean": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "brand": {
+            "type": "string"
+          },
+          "color": {
+            "type": "string"
+          },
+          "style": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "brand",
+          "style"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "match": {
+      "type": "boolean"
+    },
+    "next_step": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "type": "string"
+        },
+        "tool": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool",
+        "reason"
+      ],
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "product": {
+      "additionalProperties": {},
+      "properties": {
+        "availability": {
+          "enum": [
+            "in_stock",
+            "out_of_stock",
+            "backordered",
+            "discontinued"
+          ],
+          "type": "string"
+        },
+        "brand": {
+          "type": "string"
+        },
+        "color": {
+          "type": "string"
+        },
+        "compare_at_price_usd": {
+          "type": "number"
+        },
+        "eta_display": {
+          "type": "string"
+        },
+        "notify_url": {
+          "type": "string"
+        },
+        "preorder_available": {
+          "type": "boolean"
+        },
+        "price_usd": {
+          "type": "number"
+        },
+        "product_url": {
+          "type": "string"
+        },
+        "restock_eta_week": {
+          "type": "string"
+        },
+        "ships_today_cutoff": {
+          "type": "string"
+        },
+        "style": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "brand",
+        "style",
+        "availability",
+        "price_usd",
+        "product_url",
+        "preorder_available",
+        "notify_url"
+      ],
+      "type": "object"
+    },
+    "retailer": {
+      "type": "string"
+    },
+    "supported_brands": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "match",
+    "retailer"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real behavioral context beyond that: what each branch means (preorder_available semantics differ for availability=preorder), that discontinued colours return a next_step naming an equivalent-finding tool, and that in_stock colours confirm availability with available_quantity. It stops short of stating caching/freshness or rate limits for 'live factory availability'.

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 the core definition, then field semantics and branch handling in a logical order. It is dense with parentheticals and somewhat run-on, but nearly every clause carries operational meaning; the terms URL is a minor non-essential tail.

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?

With an output schema present, annotations covering the safety profile, and 100% schema coverage on all three required params, the description fills the remaining gaps: meaning of restock_eta_week/eta_display, the three availability branches, and what happens on discontinuation. An agent has everything needed to call and interpret it.

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 brand/style/color are already documented with examples in the schema. The description only reinforces the granularity ('one colour'), adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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: expected back-in-stock week for one colour of a specific wig brand/style, sourced from factory availability. An agent can tell this is a per-colour ETA lookup rather than a general availability check, though it never names the sibling check_stock or color_crossmatch to sharpen the boundary.

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 implied through state branches (backordered/out of stock, preorder, discontinued, in_stock), which does signal when the tool is relevant. However there is no explicit when-to-use-this-vs-check_stock guidance, and the only sibling routing mentioned is next_step inside a discontinued response, not a rule for the caller.

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

All MyHairMail Agent Tools 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?