Skip to main content
Glama

wp_commands

Read-only

Shows which WP-CLI commands the connected WordPress site permits, so you can check available read-only commands before running them.

Instructions

Show which WP-CLI commands this site allows.

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

Input Schema

NameRequiredDescriptionDefault
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds nothing beyond the one-line purpose: it does not say what "allowed" depends on (user capability, plugin set, WP-CLI availability) or what form the result takes, leaving the agent to guess at the meaning of the output.

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?

One short, front-loaded sentence with no filler or redundancy. Its brevity is a structural strength, though it borders on under-specification captured in other dimensions.

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

Completeness2/5

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

For a discovery tool with an optional, undocumented parameter and no output schema, the description should at minimum clarify the default-site behavior and the shape of the returned command list. Neither is present, so an agent cannot confidently predict the call's target or result.

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

Parameters2/5

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

The single 'site' parameter has 0% schema description coverage (anyOf string/null, default null), so the description must compensate and does not. It never mentions 'site', nor whether omitting it targets a default site, which is exactly the ambiguity an agent needs resolved.

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?

"Show which WP-CLI commands this site allows" names a specific verb (show) and resource (WP-CLI commands permitted on a site), which is distinguishable from the mutation/read siblings like 'wp' or 'site_overview'. It loses a point only because "this site" is ambiguous against the tool's own optional 'site' argument.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the obvious alternative 'wp' (which presumably runs WP-CLI commands). An agent must infer that this is a capability-discovery/pre-flight check; no exclusion or prerequisite is given.

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