Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp maintenance status

wordpress_specialist_wp_maintenance_status
Read-only

Check if WordPress is in maintenance mode by inspecting the .maintenance file, returning enabled status, start time, and whether the flag is stale after 10 minutes.

Instructions

[UNIFIED] Report whether WordPress is currently in maintenance mode by inspecting the .maintenance sentinel file. Returns enabled, started_at (epoch), and stale (true when older than 10 minutes — WP's own threshold). Requires Airano MCP Bridge v2.11.0+ and manage_options.

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_specialist_wp_maintenance_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true, and the description goes well past that: it discloses the detection mechanism (sentinel file), the exact return fields, the 10-minute staleness threshold, and two hard prerequisites (Bridge v2.11.0+ and manage_options). That is precisely the prerequisite/behavior context annotations cannot carry.

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

Conciseness5/5

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

Two sentences, purpose and mechanism front-loaded, prerequisites and return shape trailing. No filler wording; the parenthetical threshold explanation earns its space.

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 enumerates the returned keys and the stale semantics, and it states version/capability requirements. The only real gap is the undocumented 'site' parameter, which is the one thing an agent must get right to call it.

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% and the single required parameter 'site' is never explained in the description — no format, no whether it is an ID/URL/alias, no default. The description compensates fully for the return values but not for the one input the agent must supply.

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?

Names a specific verb+resource ('Report whether WordPress is currently in maintenance mode') and even the mechanism (inspecting the .maintenance sentinel file). An agent can distinguish it from sibling diagnostics like wp_db_check or wp_php_info without opening the schema.

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 implied by the purpose (check maintenance mode before/after an operation), but the description gives no explicit when-to-use or when-not-to-use guidance and names no alternative or follow-up tool.

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