Skip to main content
Glama

runloyal_read

Read the current RunLoyal page to inspect its text plus numbered buttons, links, and fields; optionally limit results to a specific element for targeted page review.

Instructions

Read the current RunLoyal 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": "runloyal_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 it discloses only that the result is a numbered inventory of page content. It says nothing about whether reading is side-effect free, whether numbering is stable across calls, size/truncation limits on large pages, or what happens if the page is still loading — all material for a browser-automation read.

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 scope, with zero filler. Everything stated is load-bearing.

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

Completeness4/5

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

With no output schema and no annotations, the description does at least characterize the return payload (text plus numbered interactive elements), which is the critical piece for this tool. Still missing is the scoping behavior of 'element', failure behavior when no page is loaded, and truncation behavior — modest but real gaps for a state-snapshot tool.

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 'element' parameter is fully documented in the schema (100% coverage), so the schema does the work. The description adds no meaning beyond it — it never explains that reading can be scoped to a single element, nor how element numbers relate to the numbered listing the tool returns.

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 — 'Read the current RunLoyal page' — and enumerates what comes back ('text and numbered buttons, links and fields'), which tells an agent this is a page-inspection tool rather than a navigation or mutation tool. It does not explicitly contrast itself with runloyal_open or runloyal_status, so it falls short of full sibling differentiation.

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: 'current page' hints that this inspects already-open state, so an agent can infer it should be called before deciding what to click or type. There is no explicit when-to-use/when-not-to-use statement, no mention of what to do if no page is open, and no pointer to runloyal_open as the alternative for a fresh navigation.

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