Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

Browse barber and beauty supply store products

shop_supplies
Read-only

Browse and search products from the barber and beauty supply stores that sell through ShearQuery: Atlanta Barber & Beauty Supply (clippers, trimmers, blades, shears, razors, disinfectant, capes, chairs) and Brighton Beauty Supply (professional hair color, developer, lightener, gel polish, nail tools, hair care), with price, stock and options. With no arguments it lists the stores. With query (and optionally store, category, in_stock_only, page) it returns matching products, each a name link with a product_id. With product_id it returns that product's details and OPTIONS (sizes, blades, colors), each with its own price and stock. When you list products, keep each one's name link exactly as given: the page is where the member sees the pictures and options. To buy, add items to their cart (update_supply_cart) or ask for a quote (request_supply_quote); nothing is bought by browsing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shop_supplies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, 12 per page. Defaults to 1.
queryNoThe member's own product words, brand AND model together, e.g. 'andis talon', 'wahl magic clip', 'wella koleston', 'welloxon 20 volume'. Never shorten to the brand alone: 'andis' alone returns 136 products and buries the one they named.
storeNoA store's name or slug, to search only that store.
categoryNoA category name from an earlier result.
product_idNoOne product's id from an earlier result, for its details and options.
in_stock_onlyNoLeave out sold-out products. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The member's own product words, brand AND model together, e.g. 'andis talon', 'wahl magic clip', 'cordless clipper'. Never shorten to the brand alone: 'andis' alone returns 136 products and buries the one they named."New value: +"The member's own product words, brand AND model together, e.g. 'andis talon', 'wahl magic clip', 'wella koleston', 'welloxon 20 volume'. Never shorten to the brand alone: 'andis' alone returns 136 products and buries the one they named."
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What to look for, e.g. 'cordless clipper', 'Wahl blade', 'Barbicide'."New value: +"The member's own product words, brand AND model together, e.g. 'andis talon', 'wahl magic clip', 'cordless clipper'. Never shorten to the brand alone: 'andis' alone returns 136 products and buries the one they named."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint true, openWorldHint false), and the description adds genuinely useful behavior: the store roster, the 12-per-page result shape, that options come with their own price and stock, and the instruction to preserve [name](page) links because the page hosts product pictures and options. This is context an agent could not infer from the annotations or schema.

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 purpose and organized as argument-mode sentences, with a closing purchase-routing note. The parenthetical product lists for each store are the longest stretch and are slightly verbose, but they do help an agent map member wording to a store, so they mostly earn their place.

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?

There is no output schema, so the description carries the return-value burden and does: it describes store listings, product results with link plus product_id, and per-option price and stock. For a 6-parameter read tool this leaves no significant gap an agent would need before calling it.

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; the description earns more by explaining how parameters combine (query with optional store, category, in_stock_only and page) and by tying product_id to 'details and options' from an earlier result. The query-composition advice (brand AND model) largely duplicates the schema text.

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 (browse and search) and resource (products from named barber/beauty supply stores), and even enumerates the two stores and their product lines. It is clearly distinguishable from write-side siblings like update_supply_cart and request_supply_quote.

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 maps argument combinations to behaviors: no arguments lists stores, query (plus optional store/category/in_stock_only/page) returns matching products, product_id returns details and options. It also names the alternatives for purchasing (update_supply_cart, request_supply_quote) and states 'nothing is bought by browsing,' which sets a clear boundary.

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.