Skip to main content
Glama

runloyal_guide

Guides users through RunLoyal tasks—pet counts, boarding bookings, report cards, owner messages, and invoices—and provides the sign-in link; call it first.

Instructions

How to work in RunLoyal (pet counts, boarding bookings, report cards, owner messages and invoices): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in RunLoyal, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/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. It discloses the content scope (screens, sign-in link, domain list) and the ordering constraint, but says nothing about what is actually returned, whether the call requires authentication, or how the response should be consumed before calling the sibling tools.

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?

Two short sentences with zero filler: the parenthetical scope list is dense but informative, and the critical instruction ("Call this first") is placed at the end as a clear directive.

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 simple one-optional-parameter guidance tool this covers most of what an agent needs: scope and call ordering. The gaps are the unexplained `task` parameter and the absence of any hint about the shape of the returned guidance, which matters since no output schema 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 `task` parameter is documented there as free-form intent, so the baseline is 3. The description never mentions the parameter or how a stated task changes the guidance returned, so it adds no meaning 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?

The description names the resource clearly: orientation content about RunLoyal's screens and sign-in link, enumerating covered domains (pet counts, boarding bookings, report cards, owner messages, invoices). The verb is soft ("How to work in"), but an agent can distinguish this guidance tool from the action siblings (runloyal_click, runloyal_type, 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 Guidelines4/5

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

"Call this first" gives explicit sequencing guidance relative to the sibling action tools, which is exactly the when-to-use signal an agent needs for an onboarding tool. It stops short of naming alternatives or stating when not to use it, but the context is clear.

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