Skip to main content
Glama

runloyal_click

Click a numbered element on the current RunLoyal page to select or activate the interface item identified by the last read.

Instructions

Click a numbered element 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>"
    },
    "name": "runloyal_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement 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 behavioral burden and mostly fails to: it does not say whether a click navigates, mutates data, is reversible, or fails on a stale element number. It also omits whether element numbering is invalidated after the click, which is critical for chaining actions.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though the brevity forgoes any structural section on preconditions or post-click state.

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?

A UI interaction tool with no annotations and no output schema needs the description to explain what changes after the click and how element references behave. None of that is present, leaving the agent to guess about page state and re-read requirements.

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 'element' parameter is fully documented as an integer >= 1 sourced from the last read. The description adds nothing beyond this, which is acceptable at the baseline for a one-parameter tool.

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 ('click') and resource ('a numbered element on the current RunLoyal page'), with a scope qualifier ('current page') that separates it from navigation tools like runloyal_open. It never explicitly contrasts with runloyal_type, which is the nearest ambiguous sibling, so it stops short of 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 Guidelines2/5

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

The single sentence gives no when-to-use or when-not-to-use guidance and names no alternatives. The only sequencing hint ('Element number from the last read') lives in the schema, not the description, so an agent gets no explicit instruction to read the page before clicking.

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