Skip to main content
Glama

salonbiz_guide

Provides step-by-step guidance on the salon platform's screens and sign-in link so you can read appointment books, review stock, and run salon reports; use it first for related tasks.

Instructions

How to work in SalonBiz (read the appointment book, review stock and run salon reports): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in SalonBiz, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it implies a read-only informational return (screens, sign-in link) but never states outright that it returns instructions rather than performing salon operations or mutating data. An agent could plausibly read "How to work in SalonBiz" as doing the work; that ambiguity is the main gap for an unannotated tool.

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?

A single sentence with a parenthetical scope list, front-loaded with the resource and ending on the imperative "Call this first." No filler, no repetition of the tool name or schema fields.

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 one-optional-parameter orientation tool with no output schema, the description covers what the tool is, roughly what it returns, and when to call it. The remaining missing element is an explicit statement that it only yields guidance and does not execute salon actions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter with 100% schema description coverage ("What you want done in SalonBiz, in your words"), so the schema already defines it. The description adds no guidance on how to phrase the task, whether it is required, or how an empty task behaves — baseline 3 applies.

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?

The description identifies this as an orientation/help resource for SalonBiz and enumerates the coverage areas (appointment book, stock, salon reports) plus concrete content (screens and the sign-in link), so an agent can tell it is documentation rather than an action tool. It does not explicitly contrast itself with the action siblings (open/click/read/type), which keeps it short of a 5.

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?

"Call this first." is an explicit, actionable ordering instruction that tells the agent to invoke this before the other salonbiz_* tools. There is no stated when-not-to-use condition or mention of what to do after reading the guide, but the primary sequencing guidance is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.