Skip to main content
Glama

salonbiz_read

Read the current SalonBiz page to extract its text and numbered interactive elements like buttons, links, and fields, enabling page understanding and navigation.

Instructions

Read the current SalonBiz page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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 burden of behavioral disclosure. It usefully says the tool exposes the current page's text plus numbered buttons, links, and fields, but it does not state whether the read is purely observational, whether it waits for the page to load, or how much content is returned. The read-only nature is strongly implied by the verb and tool name, but richer behavioral context is absent.

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

Conciseness5/5

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

The description is a single compact sentence with the core operation front-loaded. Every phrase earns its place by clarifying the resource and the kinds of content returned.

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 simple read tool with one fully documented optional parameter and no output schema. The description compensates for the missing output schema by naming the returned content types, though it could say more about prerequisites and whether the page must already be open. It is largely complete for the tool's complexity.

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 description coverage is 100%, and the single optional 'element' parameter is already documented as restricting the read to inside that element. The description does not mention the parameter or add any semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb, 'Read', and names the resource, the current SalonBiz page. It also enumerates what is returned (text, numbered buttons, links, fields), which distinguishes it from sibling action tools like click and type. It stops short of explicitly naming an alternative tool, so a 4 rather than a 5.

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?

The phrase 'current SalonBiz page' implies the tool is used to inspect an already-open page, which gives useful contextual guidance. However, it does not state when to prefer this over sibling tools such as salonbiz_status or salonbiz_guide, nor does it mention prerequisites like needing a page open first.

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