Skip to main content
Glama

Skills for your jobs

skills__list
Read-onlyIdempotent

The skills this agency has for you: step-by-step instructions for jobs, such as checking backups, writing a client report or the agency's own way of onboarding a client. Some are Royally's and some the agency wrote. Call it at the start of a job and, when a skill's description fits the job, load it with skills__get and follow it. With site_id: only the skills for that site. Names and descriptions only. Reads Royally's records only. Skills now: backup-verification: Check whether an agency's WordPress client sites are really backed up, through Royally and SiteVault, UpdraftPlus or Duplicator: which back… | bulk-seo-optimize: Change SEO titles, meta descriptions, noindex or canonical settings on many pages of a client WordPress site through Royally, safely: draft… | bulk-site-edit: Make the same content change on many client WordPress sites at once through Royally, safely: previews the change on every site, shows what… | cross-site-security-sweep: Read and explain security posture across an agency's WordPress sites in Royally: known vulnerabilities, exposed files and settings, stale s… | fleet-compatibility-check: Readiness check across an agency's WordPress sites in Royally before PHP or WordPress upgrades or an update backlog: which PHP, WordPress a… | fleet-seo-audit: Read and explain SEO health across an agency's WordPress sites in Royally, graded against the Royal SEO Standard. | post-launch-qa-checklist: Read-only QA of one WordPress client site in the hours and days after it goes live, is redesigned, moves host or changes domain, through Ro… | vulnerability-alert-triage: Turn Royally's open security alerts into decisions for a WordPress agency: what to fix first and how fast, what one alert means, a safe pla… | weekly-client-health-report: Turn Royally's stored weekly health reports for an agency's WordPress client sites into a short agency briefing and a warm, accurate client….

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": "skills__list"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoA site id from fleet/list_sites, to list only the skills for that site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds useful context beyond that: it returns names and descriptions only, reads Royally's records only, and shows only site-specific skills when site_id is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and usage guidance are front-loaded, but the description then embeds a long, volatile list of current skills with truncated descriptions. That list duplicates what the tool is meant to return and makes the definition longer than necessary.

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?

For a simple listing tool with no output schema, the description explains what is returned (names and descriptions only), where the data comes from, how site filtering works, and the next step after selecting a skill. It is complete enough for correct invocation.

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 description coverage is 100%, and the schema already explains that site_id comes from fleet/list_sites and limits results to that site. The description repeats the site filtering behavior without adding syntax or constraints beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states that this tool returns the skills available to the agency, explains that they are step-by-step instructions for jobs, and distinguishes the listing purpose from skills__get, which loads a selected skill.

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?

It gives clear usage guidance: call at the start of a job, and when a skill description fits, load it with skills__get and follow it. It also explains the site_id filter. It does not explicitly state when not to use the tool, but the intended workflow and alternative are clear.

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