Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

Accept or decline a supply quote

decide_supply_quote
Idempotent

Act on one of the signed-in member's supply orders. decision "accept" PAYS THE QUOTE'S TOTAL FROM THEIR WALLET and sends the order to be placed with the store; say the total and confirm before calling. "decline" turns a quote down (nothing is charged). "cancel" withdraws a request that hasn't been quoted yet. order_id is the 8-character order number or the full id. If the wallet is short, load it first with checkout_link.

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": {
      "order_id": "<order_id>",
      "decision": "<decision>"
    },
    "name": "decide_supply_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations say readOnlyHint=false and destructiveHint=false, but the description goes further by disclosing that 'accept' moves real money from the member's wallet and tells the agent to state the total and confirm before calling. The wallet-balance prerequisite is also surfaced. It doesn't describe what a successful response looks like, but the financial consequence and precondition are the critical behaviors here.

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

Conciseness5/5

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

Roughly four sentences, front-loaded with the highest-stakes fact (money leaves the wallet), then per-decision semantics, then the id format, then the fallback path. No filler sentences.

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

Completeness4/5

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

For a two-parameter mutation tool with no output schema, the definition covers cost, confirmation, preconditions, and identifier formats. The only omission is what result or error shape comes back, which is minor given annotations already declare idempotency and non-destructiveness.

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 0%, so the description must carry the load, and it largely does: every decision enum value is explained with its side effect, and order_id is documented as an 8-character order number or a full id. Both parameters gain meaning that the bare schema does not provide.

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?

A specific verb plus resource ('act on one of the signed-in member's supply orders') immediately scoped to the caller's own orders, with all three decision modes spelled out so an agent can distinguish this from request_supply_quote and my_supply_orders.

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

Usage Guidelines4/5

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

Each decision value carries its own when-to-use rule: 'accept' pays and forwards the order, 'decline' charges nothing, 'cancel' only applies to a request that hasn't been quoted yet. It also routes the agent to checkout_link when funds are short. It doesn't discuss viewing an order first, but the stated conditions are clear.

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.