Skip to main content
Glama

styleseat_guide

Get guidance before working in StyleSeat: learn the screens and sign-in link for appointments, refunds, reviews, and client campaigns.

Instructions

How to work in StyleSeat (appointments, refunds, reviews and client campaigns): 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": "styleseat_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in StyleSeat, 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 provided, the description carries the burden; it does disclose the content of the response (screens, sign-in link) and implies a non-mutating informational read. It says nothing about whether the guide is static or session-specific, or about any auth requirements for the sign-in link.

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; the scope list is front-loaded and the imperative 'Call this first' closes it. Slightly dense parenthetical, but nothing is wasted.

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 low-complexity guide tool with one optional param and no output schema, the description conveys the domain coverage and the sequencing role an agent needs. It could say more about what form the guidance takes (steps vs. raw screen descriptions), which is the main remaining gap.

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 a single optional parameter whose schema description ('What you want done in StyleSeat, in your words.') is already complete at 100% coverage. The description adds no format, examples, or behavior for that free-text field, so no value beyond the schema.

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 domain (StyleSeat appointments, refunds, reviews, client campaigns) and states the payload ('its screens and the sign-in link'), which distinguishes it from the action-oriented siblings like styleseat_click or styleseat_type. The verb is implicit rather than stated ('how to work in'), so an agent must infer this returns guidance rather than performing an action, but the gist is clear.

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 explicit sequencing guidance that tells the agent this tool should precede the click/type/read siblings. It does not state exclusions or what to do on repeat visits, so it falls short of a full when/when-not specification.

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