Skip to main content
Glama

runloyal_status

Check Cotlet.dev account status, available credits, and RunLoyal connection readiness before using booking, messaging, or reporting features.

Instructions

Check that your Cotlet.dev account and RunLoyal are ready: account, credits and RunLoyal connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the three things verified (account, credits, connection), which is genuine value beyond the name, but it never states that the call is read-only/non-mutating, whether it hits the network, or how failures surface.

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?

A single front-loaded clause with the checks enumerated after the colon; no redundant or filler wording. Every element earns its place.

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 no-parameter, no-output-schema health check, the description should say something about what a result looks like (pass/fail, which of the three items failed and what to do next). That is absent, so an agent can select the tool but cannot anticipate its response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline for a parameterless tool applies. No parameter meaning needs to be supplied by the description.

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 ("Check") and a concrete resource (Cotlet.dev account, credits, RunLoyal connection), so the agent knows this is a readiness/preflight probe rather than an action. It doesn't explicitly contrast with the sibling action tools (open/click/read/type), but the resource itself is clearly distinct.

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?

"Check that ... are ready" implicitly positions this as a preflight before performing RunLoyal operations, which is useful inferred guidance. It stops short of saying when not to call it, how often to call it, or naming an alternative.

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