Skip to main content
Glama

salonbridge_open

Open a SalonBridge page in your signed-in Cloud Browser to manage salon appointments, clients, payments, stock, and reports. Use it to start working inside your SalonBridge account.

Instructions

Open a SalonBridge page in your signed-in Cloud Browser (default https://online.mysalonbridge.com) to work with salon appointments, clients, payments, stock and reports.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://online.mysalonbridge.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose two meaningful traits: the operation happens inside a signed-in browser session (so authentication state is assumed) and there is a default target URL. It stops short of saying whether it navigates an existing tab or opens a new one, what happens if a page is already open, or how invalid URLs are handled.

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?

A single front-loaded sentence with the action and target in the first clause, and the default URL in parens where it belongs. The trailing list of work domains (appointments, clients, payments, stock, reports) is mildly promotional but serves to indicate the scope of pages that can be opened.

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?

This is a low-complexity tool: one optional parameter, no nested objects, no output schema, and nothing destructive claimed. The description covers what it does, where it operates, and the default target, which is sufficient to invoke it correctly; only tab-reuse behavior and failure modes are left unstated.

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% for the single optional url parameter, so the baseline applies. The description restates the default URL but adds no meaning about accepted formats, relative vs absolute paths, or behavior when the URL is omitted beyond what the schema already says.

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 a specific verb (Open) and a specific resource (a SalonBridge page in your signed-in Cloud Browser), plus the default URL and the domain it operates on. It is clearly distinguishable from siblings like salonbridge_click or salonbridge_read, which act within an already-open page, though it never says so explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: opening a page is a natural prerequisite to salonbridge_click, salonbridge_read and salonbridge_type on that page, and 'signed-in Cloud Browser' hints at an auth precondition. There is no explicit when-to-use statement, no guidance on calling it before other tools, and no note on whether it is needed once per session.

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