Skip to main content
Glama

salonbiz_type

Type text into a numbered field on the current SalonBiz page to fill forms accurately by referencing the field index from the last read.

Instructions

Type text into a numbered field on the current SalonBiz page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "salonbiz_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden: it does not say whether existing field content is cleared or appended to, whether the field must already be focused, whether permission or login is required, or what happens if the element number is stale or invalid. For a UI-mutating automation tool, these are significant omissions.

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 with no wasted words; the action and target are clear immediately. Brevity here comes at the cost of detail rather than from tight editing of a richer description.

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

Completeness2/5

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

No annotations and no output schema mean the description must explain side effects and failure modes, and it does neither. An agent does not learn whether typing is destructive to existing content or what constitutes a successful invocation.

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 coverage is 100%, so both 'element' and 'text' are already documented in the schema. The description repeats the numbered-field concept but adds no detail on element numbering validity or text formatting beyond what the schema states, 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?

States a specific verb and resource: "Type text into a numbered field on the current SalonBiz page." That is clearly distinct from salonbiz_click and salonbiz_read. It stops short of explicitly naming siblings, but the action is unambiguous.

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 through the phrase "number field from the last read," which hints at a read-then-type workflow. The description never says when this tool should be preferred over salonbiz_click or when it should not be used, such as on non-input elements or without a prior read.

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