Skip to main content
Glama

ShearQuery — Barber & Beauty Industry Data

A Stripe link to load the wallet or buy a plan

checkout_link

Get a secure Stripe checkout link for the signed-in member, for one of two things. for: "wallet" loads their wallet with $5, $10, $25, $50, $100, $250 (amount_dollars). for: "plan" buys the Manage or Autopilot plan (plan) at their account type's monthly price; say that price, from the result, when giving the link. NOTHING IS CHARGED BY THIS TOOL: they pay on Stripe's page, and the balance or plan updates a few seconds after. Give the link exactly as returned. Never ask for or accept card details in the conversation. Only set auto_reload when the member has clearly asked for automatic reloads; it lets ShearQuery charge the same card the same amount when the balance runs low, at most once a day. A member who ALREADY has a paid plan is not switched; the result gives the page where switching and cancelling are done.

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": {
      "for": "<for>"
    },
    "name": "checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
forYesWhat the link pays for.
planNoFor a plan: the one they chose.
auto_reloadNoFor the wallet: true ONLY if the member asked for automatic reloads. Defaults to false.
amount_dollarsNoFor the wallet: how much to load, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / amount_dollars / enum
      Previous value: -[
      -  5,
      -  10,
      -  25
      -]New value: +[
      +  5,
      +  10,
      +  25,
      +  50,
      +  100,
      +  250
      +]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only mark this as non-read-only, open-world, non-idempotent, non-destructive; the description adds the important context that nothing is charged by the tool itself, payment happens on Stripe's page, and the balance or plan updates a few seconds later. It further discloses that auto_reload authorizes recurring charges of the same amount on the same card at most once per day, and that the result contains the price and a page for switching or cancelling. This is materially more than the annotations convey.

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?

The key constraints — nothing is charged, give the link exactly as returned, never take card details — are front-loaded and easy to scan, with each sentence carrying an operational rule. The phrasing is occasionally run-on ("for: "wallet" loads...") and mixes formatting with prose, which slightly reduces readability, but there is little true 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?

There is no output schema, yet the description covers what the agent needs from the result: the price to quote and a page for switching or cancelling an existing plan. Combined with the no-charge semantics, deferred payment, and delayed balance update, the definition is complete for a 4-parameter link-generation tool.

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, but the description adds real meaning: it spells out which values apply to which for: mode, that amount_dollars is the load amount on the wallet flow, and the behavioral consequence of auto_reload (repeat charge of the same amount, at most daily) plus the strict condition for setting it. The only thing not elaborated is the exact plan enum semantics beyond naming Manage and Autopilot.

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 ("Get a secure Stripe checkout link for the signed-in member") and immediately splits the two supported modes, wallet top-up versus plan purchase. It also names the sibling-adjacent resources it interacts with (wallet balance, Manage/Autopilot plans), so an agent can tell exactly which task this tool serves.

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?

The description gives explicit branching rules: use for:"wallet" to load funds, for:"plan" to buy Manage or Autopilot at the account type's monthly price. It also states exclusions and prerequisites — never accept card details, only set auto_reload when the member clearly asked, and an existing paid-plan member is not switched. That is when-to-use, when-not-to, and alternative-path guidance all in one.

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.