Skip to main content
Glama

royal-mcp__wp_get_option

Read-onlyIdempotent

Get a single WordPress option value. Requires manage_options capability. The option name must be in the readable allowlist — 13 defaults (blogname, blogdescription, siteurl, home, admin_email, posts_per_page, date_format, time_format, timezone_string, googlesitekit_analytics-4_settings, show_on_front, page_on_front, blog_public) plus any keys plugin authors opt in via the royal_mcp_readable_options filter, plus options an admin allowlists under Royal MCP Pro settings (Allowlisted plugin options) while option writes are enabled. Values are masked: values under credential-like names (keys, secrets, passwords, tokens) and values shaped like credentials are redacted; a short random value stored under an ordinary name cannot be told apart from normal data and is returned. An administrator can list an allowlisted option under Return as stored (Royal MCP Pro settings); its value is then returned unmasked, except that credential fields, provider key formats, private keys and credentials in links inside it stay hidde… Through Royally: read-only, runs straight away.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "royal-mcp__wp_get_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavior beyond them: masking rules for credential-like names and values, the caveat that a short random value under an ordinary name cannot be distinguished, and the admin 'Return as stored' exception. The trailing 'read-only, runs straight away' line merely restates the annotations but does not conflict with them.

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 purpose and allowlist constraint are front-loaded, but the middle paragraph is dense and run-on, and the final sentence 'Through Royally: read-only, runs straight away' duplicates the annotations. The text also appears truncated mid-word ('hidde…'), which hurts polish.

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 two-parameter read tool with no output schema, the definition covers everything an agent needs: capability gate, accepted keys, masking behavior, and the conditions under which masking is bypassed. Nothing material about correct invocation is left to inference.

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

Parameters5/5

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

With only 50% schema coverage, the description compensates heavily for the undocumented 'name' parameter by enumerating all 13 default allowlisted keys and explaining how plugin authors or admins extend the list. It also makes clear that out-of-allowlist names will not resolve, which the schema does not convey.

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 opening sentence gives a precise verb and resource: 'Get a single WordPress option value.' That cleanly separates it from the write sibling (wp_update_option) and from the many other read tools that target different resources such as wp_get_plugins or wp_get_global_styles.

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 states explicit prerequisites — 'Requires manage_options capability' and 'The option name must be in the readable allowlist' — plus the three ways a key gets allowlisted. What it lacks is an explicit statement of when to prefer this tool over an alternative, though the read-versus-write distinction is clear enough from the name.

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