Skip to main content
Glama

royal-mcp__sv_get_dashboard_summary

Read-onlyIdempotent

[Royal MCP Pro] Composite read: SiteVault Pro backup health at a glance for orchestrator dashboards. Returns latest backup age, backup counts (total/completed/failed) and retention target, scheduler state (next-run + on-track/overdue), and storage-provider status. on_track is false when the next scheduled run is an hour or more overdue (overdue_by_hours above 0), when SiteVault reports a schedule stale or without its cron event, or when a backup made by a schedule failed after the newest completed backup (failed_scheduled_at); a failed manual backup leaves it alone. Every time is in UTC. Graceful degradation: { active: false } when SiteVault is not installed or active. Requires manage_options. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

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": "royal-mcp__sv_get_dashboard_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only establish read-only/idempotent/non-destructive; the description adds substantial context beyond them: an explicit permission requirement ('Requires manage_options'), the degradation contract ({ active: false } when SiteVault is missing or inactive), UTC-only timestamps, and a precise definition of when on_track flips false. That on_track rule set (overdue by an hour or more, stale schedule or missing cron event, failed scheduled backup after the newest completed one, manual failures excluded) is exactly the kind of behavioral detail an agent cannot get from the annotation block.

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?

Purpose is front-loaded in the first sentence and each subsequent sentence carries distinct payload (return fields, on_track rules, timezone, degradation, auth). The long parenthetical on on_track and the '[Royal MCP Pro]' branding prefix and trailing '(site: ...)' / 'Through Royally:' boilerplate are mild overhead but the body earns its length.

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

Completeness5/5

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

With no output schema, the description carries the full burden of explaining return values, which it does by naming each field group and defining derived flags like on_track and overdue_by_hours. Auth, timezone, and the degraded-response shape round out everything an agent needs before invoking it.

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?

There is only one parameter (site_id) and schema description coverage is 100%, with the enum value and its target site already documented in the schema. The description adds nothing about site_id, so the baseline of 3 applies; it neither compensates nor detracts.

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?

It gives a specific verb ('Composite read') plus a precise resource ('SiteVault Pro backup health') and enumerates exactly what is returned: backup age, counts, retention target, scheduler state, storage-provider status. The phrase 'at a glance for orchestrator dashboards' signals it is an aggregator rather than a granular listing, which differentiates it in spirit from siblings like sv_get_backups or sv_get_schedules without naming them.

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 through 'for orchestrator dashboards' and the graceful-degradation rule for when SiteVault is not installed or active, but there is no explicit statement of when to prefer this over sv_get_backup_status, sv_get_backup, or sv_get_schedules. An agent must infer the aggregate-vs-detail split from the phrase 'at a glance'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources