Skip to main content
Glama

fort_cache_purge

Purge a Bearfort-hosted site's nginx page cache, flush its object-cache keys, and reset OPcache to clear stale content after WordPress changes.

Instructions

Purge the fort's nginx page cache (through Bearfort's cache-purge service, the same request WordPress itself makes on content changes), flush the fort's own object-cache keys and reset OPcache. details says 'Page cache: purged', or 'requested' if the purger had not run yet (it runs every 2 s). Needs BEARFORT_API_KEY and Bearfort fleet 2026-10-08.3+ (before that the page cache was not actually purged).

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": "fort_cache_purge"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites); must be hosted on Bearfort

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the three distinct effects, the mediating service, eventual consistency ('requested' vs 'purged', purger runs every 2 s), required credentials, and a fleet-version floor below which the page cache was not actually purged. It stops short of stating idempotency, rate limits, or whether a purge can disrupt live traffic.

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?

Front-loaded with the core action, then prerequisites and status semantics in supporting sentences; nearly every clause earns its place. It is a dense run-on sentence rather than a structured list, which slightly hurts scanability.

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

Completeness5/5

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

For a one-parameter tool with no annotations and no output schema, the definition supplies what an agent actually needs: preconditions (API key, fleet version), the async status semantics of the response, and the exact effects performed. Nothing essential to a correct invocation appears missing.

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 single 'site' parameter is fully documented in the schema (site id, see list_sites, must be Bearfort-hosted). The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

The description uses precise verbs and resources — purge nginx page cache, flush object-cache keys, reset OPcache — and even names the underlying service the request goes through. It does not, however, distinguish itself from the sibling mcp_flush_cache, whose name suggests overlapping behavior, so an agent must infer the boundary.

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 rather than stated: noting it makes 'the same request WordPress itself makes on content changes' signals the post-edit scenario. There is no explicit when-not-to-use guidance and no named alternative for the closely-named mcp_flush_cache sibling.

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