Skip to main content
Glama

salonbiz_open

Opens a SalonBiz page in your signed-in Cloud Browser so you can read the appointment book, review stock, and run salon reports.

Instructions

Open a SalonBiz page in your signed-in Cloud Browser (default https://central-app.salonbiz.com) to work with read the appointment book, review stock and run salon 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": "salonbiz_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://central-app.salonbiz.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It mentions the signed-in Cloud Browser prerequisite, which is genuinely useful, but says nothing about whether opening navigates the existing tab or adds a new one, whether callers must close it via salonbiz_close, or what an invalid URL yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and default host, which is good structure. However the trailing clause is garbled ("to work with read the appointment book") and the list of tasks muddles rather than sharpens the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter navigation tool with no output schema, the description covers the essentials of what it does and the default target. Missing is lifecycle context: whether a session/page must be opened before other salonbiz_* tools and whether it should be closed afterwards.

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% with a single optional url parameter whose default is documented in both places, so the baseline is already met. The description reinforces the default host but adds no format guidance such as path-only vs full URL, so it does not exceed the schema's contribution.

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 and resource: opening a SalonBiz page in the signed-in Cloud Browser, with the default URL given. It also names the downstream work (appointment book, stock, reports), which distinguishes it from siblings like salonbiz_read or salonbiz_click, though it doesn't explicitly say it must precede them.

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?

Implies this is the entry point for a session (open a page, then work in it) and that a signed-in Cloud Browser is required, but never states when to use this versus calling salonbiz_click/salonbiz_read directly, nor what happens if a page is already open.

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