Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

Your supply orders

my_supply_orders
Read-only

The signed-in member's supply store orders, newest first: quotes waiting for their decision (with the total), orders being placed, the store's order number and tracking once shipped, and cancellations. Also their wallet balance. Use it when they ask about a quote, an order or a delivery.

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": "my_supply_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that - newest-first ordering and the exact status buckets returned (awaiting decision, being placed, shipped with tracking, cancelled) - but says nothing about pagination, empty-state behavior, or whether history is bounded.

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?

Two sentences, front-loaded with the resource and its scope, with the enumeration of returned record types earning its space by telling the agent what it will actually get. No filler or restatement of the title.

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?

With no parameters and no output schema, the description carries the burden of describing returns, and it does so by naming each record category and the wallet balance. A note on result volume or ordering stability would close the remaining gap.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to carry. The schema coverage is 100% trivially, and nothing is left ambiguous about inputs.

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 the concrete resource ('the signed-in member's supply store orders') and enumerates the record types it returns: pending quotes with totals, in-flight orders, store order number/tracking, cancellations, plus wallet balance. That distinguishes it from action siblings like decide_supply_quote and request_supply_quote, though the included wallet balance overlaps my_wallet without acknowledging it.

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?

Explicitly tells the agent when to reach for it: 'when they ask about a quote, an order or a delivery.' It gives positive triggers but no exclusions or named alternatives, so the agent must infer whether quote actions belong to decide_supply_quote instead.

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.