Skip to main content
Glama

royal-mcp__mcp_get_skill

Read-onlyIdempotent

Read a skill: the site owner's chosen instructions for one kind of work on this site (for example editing Elementor pages or changing WooCommerce products). Read the skill before you start that kind of work and follow it. Without arguments it lists the skills loaded on this site. With a skill it returns the core of that skill and the list of its workflows; with a skill and a section it returns that one workflow. (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__mcp_get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoSkill id from the list, for example "elementor". Leave out to list the loaded skills.
sectionNoId of one workflow of the skill, from the list in the skill's core. Leave out for the core.
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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds useful behavior not in them: the tiered return shape per argument combination (list, core + workflow list, single workflow). The trailing 'read-only, runs straight away' largely restates annotations, and unknown-skill error behavior is unstated.

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?

Front-loaded with the core definition, then the when-to-use rule, then the mode breakdown — a sensible progression with little waste. The parenthetical site string and 'Through Royally' marketing line are tangential but short.

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?

With no output schema, the description carries return-value explanation and does so well for all three modes, including an example skill id. It stops short of covering invalid-argument behavior or the size/shape of the skill core, which matters for a guidance-reading tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by mapping the absence/presence of 'skill' and 'section' to distinct outputs, explaining the enumeration relationship between a skill's core and its workflows. Site_id gets no added explanation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read a skill') and defines the resource in domain terms ('the site owner's chosen instructions for one kind of work on this site', with Elementor/WooCommerce examples). This clearly separates it from the elementor_* and wp_get_* siblings, which read live site data rather than owner-authored guidance.

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?

Gives explicit timing guidance ('Read the skill before you start that kind of work and follow it') plus the selection rule across its three invocation modes. No when-not guidance or named alternative tool, which keeps it just short of a 5.

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