Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp db optimize

wordpress_specialist_wp_db_optimize
Destructive

Optimize only current-prefix WordPress database tables through Airano MCP Bridge and return per-table optimization results.

Instructions

[UNIFIED] Optimize WordPress database tables via the Airano MCP Bridge companion plugin. Runs OPTIMIZE TABLE only on tables with the current WordPress table prefix and returns per-table results. Requires Airano MCP Bridge v2.18.5+ 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_db_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known; the description adds real context on top: it only touches prefix-matching tables, returns per-table results, and requires Airano MCP Bridge v2.18.5+ plus the manage_options capability. It stops short of describing locking/downtime or failure behavior, which matters for a table-rebuild operation.

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?

Three tight sentences, front-loaded with purpose, then scope/return, then prerequisites. Only the '[UNIFIED]' tag prefix is non-informative overhead; otherwise every clause carries content.

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 destructive maintenance operation with no output schema, the definition covers prerequisites, scope restriction, and result shape, which is a reasonable base. It leaves out the meaning of the required 'site' argument and any operational caveats (table locking, runtime, behavior on non-matching tables), so an agent could still call it blind.

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 parameter 'site' has 0% schema description coverage and is never mentioned in the description, so nothing explains what identifier format it expects or how it selects a target site in a multisite setup. With one undocumented parameter the description should compensate, and it does not.

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 ('Optimize WordPress database tables') and narrows scope to tables carrying the current WordPress table prefix, plus names the underlying operation (OPTIMIZE TABLE). That is enough to separate it from siblings like wp_db_check, wp_db_size, or wp_db_tables, though it never names those alternatives 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: an agent can infer this is a maintenance action to run after inspecting the database. There is no explicit when-to-use/when-not guidance (e.g., run after wp_db_check, avoid during peak traffic), nor any statement about which sibling to use for inspection first.

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