Skip to main content
Glama

salonbridge_read

Read the current SalonBridge page, including its text and numbered buttons, links and fields. Optionally limit reading to a single element to inspect page structure.

Instructions

Read the current SalonBridge 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": "salonbridge_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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. It does disclose the shape of the returned observation (text plus numbered buttons, links and fields), which is genuinely useful and hints that indexed elements are what click/type consume. It omits whether reading is side-effect free, what happens with no page open, and whether the numbering persists across calls.

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?

One compact sentence, front-loaded with the verb and resource, then the observable contents. Every clause contributes and there is no filler.

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 read tool with no annotations and no output schema, the description covers the essentials of what is returned. It stops short of the operational context an agent needs, notably the precondition of an open page and how the element numbering relates to the click and type siblings.

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?

The single optional parameter already has a 100% schema description ("Read only inside this element."), so the schema does the heavy lifting. The description adds nothing about the element argument, such as whether the index is a page-level or nested reference, so the baseline 3 applies.

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?

"Read the current SalonBridge page" names a specific verb and resource, and the enumeration of text, numbered buttons, links and fields tells an agent what it observes rather than mutates. That clearly separates it from sibling verbs like click, type, open and close, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no statement that a page must already be open, no indication of when to prefer this over salonbridge_status or salonbridge_guide, and no exclusions. The only cue is the word "current," which leaves the agent to infer prerequisites.

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