Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp db check

wordpress_wp_db_check
Read-only

Checks WordPress database tables through the companion plugin, running CHECK TABLE only on tables with the current WordPress table prefix to verify database integrity.

Instructions

[UNIFIED] Check WordPress database tables through the companion plugin. Runs CHECK TABLE only on tables with the current WordPress table prefix.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true is already supplied, and the description usefully reinforces it by naming CHECK TABLE (a non-mutating MySQL operation) and limiting scope to current-prefix tables. It does not disclose what the response contains (per-table status, corruption flags), whether it repairs anything, or that it depends on the companion plugin being active — a real prerequisite left implicit.

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?

Two tight sentences, with the primary action front-loaded and the scope constraint immediately after. The bracket tag adds no meaning but costs only a few tokens.

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

Completeness3/5

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

For a one-parameter read-only diagnostic with no output schema, the description covers the operation and its table scope but omits the plugin dependency and any indication of what a check result looks like, which matters for a tool whose whole value is its report.

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 'site' parameter is never mentioned in the description. Whether 'site' expects a URL, a site ID, or a slug is left entirely undocumented in both schema and prose, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Check WordPress database tables') and adds scope ('CHECK TABLE only on tables with the current WordPress table prefix') plus the mechanism ('companion plugin'). That clearly separates it from wp_db_optimize or wp_db_size, though it never names a sibling explicitly and the '[UNIFIED]' prefix is unexplained noise.

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 when-to-use or when-not-to-use guidance and no mention of the adjacent optimize/size/search tools in the sibling set. The agent must infer from the verb 'check' that this is a diagnostic/integrity operation, and it is never told what to do with the result or what prerequisite (plugin installed, credentials) is required.

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