Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

Get a quote for a supply order

request_supply_quote

Ask for a quote on supply store products for the signed-in member. ShearQuery's agent prices the order on the store's own site, usually in a few seconds, with the store's real shipping and tax for the address; if it can't, a person quotes it soon and it shows in my_supply_orders. NOTHING IS CHARGED OR ORDERED by this tool. Either from_cart: true to quote what's in their cart (my_supply_cart), or items: product_id from shop_supplies, qty, and option (the option's label exactly as shop_supplies listed it) for any product that has options. All items must be from one store. ship_to is a US address; ask the member for it (name, street, city, two-letter state, ZIP; phone optional) rather than guessing, and read it back before calling. After a quote, tell them the total line by line and ask whether to accept (decide_supply_quote), which pays from their wallet.

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": {
      "ship_to": "<ship_to>"
    },
    "name": "request_supply_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything the member wants to add (optional).
itemsNo
ship_toYes
from_cartNoQuote what's in the member's cart (my_supply_cart) instead of items. The quoted items leave the cart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from_cart
      Added value: +{
      +  "description": "Quote what's in the member's cart (my_supply_cart) instead of items. The quoted items leave the cart.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "items",
      -  "ship_to"
      -]New value: +[
      +  "ship_to"
      +]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by declaring 'NOTHING IS CHARGED OR ORDERED', describing the pricing mechanism (ShearQuery's agent prices on the store's own site with real shipping and tax), typical latency, and the human-quote fallback surfacing in my_supply_orders. It also discloses the non-obvious side effect that quoted items leave the cart — a detail no annotation conveys.

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-loads purpose, then the safety guarantee, then the input modes, then the post-call handoff — a sensible priority order. It is dense and a little long as a single paragraph, but nearly every clause carries operational information rather than filler.

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 multi-step, nested-parameter, no-output-schema workflow, the description supplies the missing pieces: where the inputs come from, address handling, what happens after a quote, and the handoff to decide_supply_quote. An agent could execute the full flow from this text alone.

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 50%, and the description compensates for most of it: it explains the from_cart/items dichotomy, the exact-label requirement for option values as listed by shop_supplies, and the contents of ship_to including the two-letter state and optional phone. Only the optional note parameter is left to the schema, which already documents it, so the coverage gap is largely closed.

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 — asking for a price quote on supply store products for the signed-in member — and immediately scopes it against the sibling that acts on a quote (decide_supply_quote, which pays). An agent can tell this is the pricing step, not the purchasing step, without opening the 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?

Gives explicit branching: either from_cart: true (quoting my_supply_cart) or an items list drawn from shop_supplies. Adds the constraint that all items must come from one store, that ship_to must be a US address gathered from the member rather than guessed, and that the total should be read back and the member asked whether to accept via decide_supply_quote.

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.