Skip to main content
Glama

runloyal_type

Types text into a numbered field on the current RunLoyal page, enabling agents to fill form inputs by referencing the field number from the last read.

Instructions

Type text into a numbered field on the current RunLoyal 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": "runloyal_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

C2.9/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 disclosure burden, and it omits key behaviors: whether existing field content is replaced or appended, whether typing triggers form submission or change events, what happens on an invalid field number, and whether the result is verified. 'Current page' hints at state dependence but nothing more.

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 filler; the action and target come first. It is efficient, though the brevity edges into under-specification rather than pure conciseness.

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 two-parameter browser-automation tool with no annotations and no output schema, the description is minimally viable: it identifies the action and target but leaves state prerequisites and outcome behavior unexplained. Nothing an agent strictly needs to invoke it is contradicted, but meaningful gaps remain.

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 parameters are already documented, and the description only loosely restates them ('type text', 'numbered field'). It adds no format, escaping, or length guidance beyond the schema, so the baseline of 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 concrete verb and resource — 'Type text into a numbered field' — which is clearly distinguishable from runloyal_read and runloyal_click by the fact that it targets a numbered field with text. It stops short of explicitly naming a sibling, so it is clear but not maximally differentiating.

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 explicit statement of when to use this versus runloyal_read or runloyal_click, nor any prerequisite like needing a prior read to obtain the field number. Usage is only weakly implied by the phrase 'on the current RunLoyal page'.

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