Skip to main content
Glama

runloyal_open

Open a RunLoyal page in your signed-in Cloud Browser to manage pet counts, boarding bookings, report cards, owner messages, and invoices.

Instructions

Open a RunLoyal page in your signed-in Cloud Browser (default https://www.runloyal.com) to work with pet counts, boarding bookings, report cards, owner messages and invoices.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.runloyal.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that the browser is already signed in (auth handled) and that a default URL applies when none is given, but it says nothing about what happens to an already-open page, whether navigation replaces existing state, or error behavior.

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 the action first and the default URL in parentheses. The enumerated use cases are slightly verbose but do real orientation work for an agent unfamiliar with the product.

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?

For a one-optional-parameter navigation tool with no output schema, the description covers action, environment, and default target. The main remaining ambiguity is whether this call returns page content or only confirms navigation — but that gap is modest given the sibling runloyal_read exists.

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 single parameter already documents its default, so the description only restates it. No additional format expectations (absolute vs relative URL, allowed hosts) are added.

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 ('Open') and resource ('RunLoyal page') and names the context ('signed-in Cloud Browser') plus the default URL. The enumerated work areas (pet counts, boarding bookings, report cards, messages, invoices) make the domain unambiguous, though it does not explicitly position itself against siblings like runloyal_read.

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 implied rather than stated: the agent is told it opens a page 'to work with' various data, but there is no explicit when-to-use, no prerequisite ordering (e.g., call this before runloyal_read/runloyal_click), and no exclusions against alternatives.

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