Skip to main content
Glama

royal-mcp__gp_get_dashboard_summary

Read-onlyIdempotent

[Royal MCP Pro] Composite read: GuardPress security posture at a glance for orchestrator dashboards. Returns failed logins (24h + 7d), blocked addresses (active_count: lockouts running now; block_list_count: permanent entries on the GuardPress block list), new security alerts (24h + 7d), 2FA enrollment rate (users enrolled / total), and threat-intel cache status (CISA KEV + Wordfence). Graceful degradation: { active: false } when GuardPress 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__gp_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.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, yet the description still adds real behavioral context: the exact return payload, the distinction between active_count (live lockouts) and block_list_count (permanent block list entries), the { active: false } degradation shape when GuardPress is absent, and the manage_options capability requirement. This is unusually rich disclosure beyond structured fields.

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 clause, followed by the return payload, then degradation, permission, and site context in a logical order. The parenthetical site note and the 'Through Royally' tag are mildly extraneous but the density is high and nothing is padded.

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?

There is no output schema, so the description carries the return-value burden and does so completely, defining each metric and the degradation shape. Combined with the permission requirement and the read-only/instant-execution note, an agent has everything needed to call and interpret this 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?

Schema coverage is 100% and the single site_id parameter is fully documented with an enum and URL in the schema, so the schema does the heavy lifting. The description's only nod to the parameter is a trailing '(site: demo.royalplugins.com)' note, which adds no syntax or selection semantics; baseline 3 applies.

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: 'Composite read: GuardPress security posture at a glance,' and enumerates exactly what is aggregated (failed logins, blocked addresses, alerts, 2FA rate, threat-intel cache). The word 'Composite' signals it bundles data that siblings like gp_get_failed_logins or gp_get_security_stats return individually, but no sibling is named explicitly, so an agent must infer the boundary.

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?

'For orchestrator dashboards' and 'at a glance' give clear context for when this tool is the right pick over per-metric calls, and the Graceful degradation note tells the agent what to expect on non-GuardPress sites. It stops short of explicit when-not-to-use guidance or naming an alternative tool.

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