Skip to main content
Glama

salonbridge_type

Types text into a specified numbered field on the current SalonBridge page, enabling AI agents to fill forms or update fields after reading their field numbers.

Instructions

Type text into a numbered field on the current SalonBridge 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": "salonbridge_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.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and falls short. It doesn't say whether existing field content is replaced or appended to, whether typing fires change/submit events, what happens if the field index is stale, or what a failed type returns.

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 sentence, front-loaded with the verb and target, with no filler or redundant restatement of the tool name. Nothing in it needs trimming.

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?

For a stateful mutation with no annotations and no output schema, the description should disclose whether it overwrites text and what page state it requires. Those gaps leave an agent guessing on a two-parameter but state-dependent action.

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% and the schema already explains both parameters, so the baseline is 3. The description reinforces that the element is a field number on the current page, but adds no format or validity detail 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?

Names a specific verb and resource: typing text into a numbered field on the SalonBridge page. The mechanism (numbered field, referencing an index rather than a selector) distinguishes it from a click or read tool, 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 Guidelines3/5

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

"On the current SalonBridge page" implies the prerequisites (page must be open, and a field number must come from a prior read), but it never states when to use this versus clicking or what to do when no valid field number exists.

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