Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Probe capabilities

wordpress_probe_capabilities
Read-only

Probe a WordPress site's companion plugin to discover the calling app password's effective capabilities and installed companion routes; returns companion_available false when missing or outdated.

Instructions

[UNIFIED] Probe the airano-mcp-bridge companion plugin for the effective capability set of the calling application password plus the list of companion routes the installed version ships. Returns companion_available: false when the plugin is missing or outdated. Cached 24 h per (site, user).

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": {
      "site": "<site>"
    },
    "name": "wordpress_probe_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real behavioral context beyond that: the false-when-missing/outdated return value and a 24-hour cache scoped per (site, user). It does not spell out auth requirements or failure modes beyond the missing-plugin case, but the added disclosure is meaningful.

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?

A single dense, front-loaded sentence covering purpose, return signal, and cache semantics; the leading "[UNIFIED]" tag is minor noise but the rest earns its place with no filler.

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 usefully names what comes back (capability set, companion routes, `companion_available`), which is the right level for a one-parameter read-only probe. The only real gap is the unexplained `site` parameter shape.

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?

Schema description coverage is 0% for the single required `site` parameter, so the description carries the full burden. It only implies site scope via the caching phrase "per (site, user)" and never explains the parameter's format (URL, ID, alias) or how to obtain it.

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 (Probe) and a specific resource (the airano-mcp-bridge companion plugin's effective capability set and shipped companion routes). An agent can distinguish this from siblings like wordpress_probe_upload_limits because the object of the probe is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the notion of probing capabilities and checking `companion_available` suggests a preflight check, but the description never states when to call it versus alternatives or what to do when the result is false. No exclusions or prerequisites are given.

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

Deploy Server

Other Tools