Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_maint_db_update_routine

Destructive

Trigger the WooCommerce database upgrade routine in the background; back up first and do not assume completion. Ask the user for confirmation before calling with confirm=true.

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_id": "<site_id>",
      "confirm": "<confirm>"
    },
    "name": "wc_maint_db_update_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true only after explicit user confirmation.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the routine runs in the background, that completion must not be assumed, and that a backup is a prerequisite. These are exactly the operational traits an agent needs for a destructive, non-idempotent call and are not recoverable from the annotation flags alone.

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?

A single tight sentence with the action first, then the safety constraints. No filler, and the most important warning (back up, get confirmation) is not buried.

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?

Covers action, async behavior, confirmation gate, and backup prerequisite, which is sufficient for a destructive tool with annotations and no output schema. A minor gap is how to verify success afterwards, which a sibling verify tool could provide.

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

Parameters3/5

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

Schema coverage is 100%, and the description's note about confirm=true largely restates the schema's own 'Must be true only after explicit user confirmation'. It adds no new meaning about site_id or value formatting beyond what the schema already states.

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?

Specific verb and resource: 'Trigger the WooCommerce database upgrade routine'. It is clearly distinguishable from sibling maintenance tools like verify_db_tables or regenerate_product_lookup_tables, though it never names an alternative to contrast against.

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

Usage Guidelines4/5

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

Gives concrete pre-call guidance: back up first, obtain explicit user confirmation, and only then pass confirm=true. It does not mention when not to use it or which sibling to run instead if the site is already on the latest schema version.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources