Skip to main content
Glama

salonbridge_guide

Explains how to navigate SalonBridge, manage appointments, clients, payments, stock and reports, and locate the sign-in link. Call it first for step-by-step guidance inside the app.

Instructions

How to work in SalonBridge (salon appointments, clients, payments, stock and 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": "salonbridge_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 disclosure burden. It implies a read-only informational tool and indicates the kind of content returned (screens and sign-in link), but says nothing about output format, whether a sign-in link is generated per session or static, or whether the optional task parameter alters what comes back.

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?

Two compact sentences with no filler; the scope is front-loaded in the parenthetical. The most important instruction ('Call this first') sits at the end rather than the start, which is a minor structural weakness.

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 simple one-optional-parameter orientation tool with no output schema, the description does enough: it states coverage and sequencing. It could say more about expected return shape, but nothing an agent needs in order to invoke it correctly is missing.

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?

Schema coverage is 100%, so the single optional 'task' parameter is already documented as free-form intent. The description does not reference this parameter at all, so it adds no meaning beyond the schema — the baseline of 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 names the resource (SalonBridge) and the specific content it covers — screens, the sign-in link, and the domains of appointments, clients, payments, stock and reports. It distinguishes itself from the UI-action siblings (click, type, read) by being orientation material, though it never uses an explicit verb like 'get' or 'explain'.

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?

The closing imperative 'Call this first' is an explicit, actionable directive that establishes this as a prerequisite/orientation step before using other SalonBridge tools. There is no statement of when-not to call it or what to do after, which keeps it just below a 5.

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