Skip to main content
Glama

check_cache_config

Start a cache configuration diagnostic ("config check") of one of your validated sites. CacheBoost sends about 40 test requests to the site (home page and sample pages, mobile and logged-in variants, static assets), adds the site's Cloudflare settings and WordPress plugin snapshot when they are connected, and scores how well pages and assets are cached. The check is asynchronous (usually under a minute): this returns {id, status: "pending"}, then poll get_config_check with that check_id until status is "done" or "error". One check at a time per site and at most 10 per site per 24 hours; it does not consume the warm quota. Requires the sites:write scope.

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>"
    },
    "name": "check_cache_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesID of the site to check (must belong to the API key and be validated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so: it discloses the ~40 test requests and what they cover, the enrichment from Cloudflare/WordPress plugin data, the asynchronous return shape {id, status: "pending"}, the one-at-a-time and 10-per-24h rate limits, quota non-consumption, and the required sites:write scope. This is exactly the behavioral context an agent needs before invoking.

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?

Front-loaded with the action, then the test scope, then the async follow-up, then the operational limits — a logical order with no filler. Every clause carries operational information the agent would otherwise have to guess.

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?

The tool is asynchronous with no output schema, and the description compensates by describing the immediate return value and the polling contract, plus limits and permissions. Nothing an agent needs to call it correctly and handle the response is 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?

There is a single parameter with 100% schema description coverage that already states the site must belong to the API key and be validated, so the schema does the heavy lifting. The description reinforces the 'validated site' constraint and the per-site serialization limit but adds no new syntax or format detail beyond the schema, making 3 the appropriate baseline.

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?

States a specific verb and resource ('Start a cache configuration diagnostic ... of one of your validated sites') and immediately disambiguates from the sibling poller by defining the two-step flow with get_config_check. An agent can distinguish this from get_config_check, warm_site, and list_runs from the description alone.

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

Usage Guidelines5/5

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

Gives explicit preconditions (site must be validated), the exact follow-up action ('poll get_config_check with that check_id until status is "done" or "error"'), and the concurrency/throughput limits. It also notes the check does not consume the warm quota, which implicitly separates it from warm_site.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources