Skip to main content
Glama

salonbiz_status

Verify your Cotlet.dev account, credits, and SalonBiz connection status. Ensure all prerequisites are confirmed to enable the SalonBiz MCP server's full functionality.

Instructions

Check that your Cotlet.dev account and SalonBiz are ready: account, credits and SalonBiz connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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, and it does disclose the three things being verified (account, credits, SalonBiz connection), which is genuinely useful context. However, it does not say whether the call is read-only, whether it consumes credits, or what a failure result looks like; the low risk of a zero-parameter call softens but does not remove that gap.

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 that leads with the verb and the outcome being verified. Minor redundancy between "your Cotlet.dev account" and the trailing "account, credits and SalonBiz connection" list costs a little, but nothing is bloated.

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?

The tool is simple (no params, no nested objects), so the description is nearly sufficient, but with no output schema and no annotations an agent still cannot tell what shape the result takes (pass/fail flags, error text, remediation hints). Adding a sentence about the response and follow-up on failure would close the gap.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated items (account, credits, connection) describe what is inspected rather than inputs, which is the right use of the space.

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 a specific verb ("Check") and a concrete resource (Cotlet.dev account status, credits, SalonBiz connection), which is clearly distinct from the sibling browser-action tools (click, open, type, read). It stops short of explicitly contrasting itself with those siblings, so an agent must infer that this is a diagnostic rather than an action.

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: "Check that ... are ready" suggests a pre-flight/readiness step before invoking the action tools, but the description never states when to call it versus alternatives, or what to do on failure. No explicit when-not guidance is given.

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