Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

pressable_toggle_edge_cache_defensive_mode

Activate or deactivate defensive edge caching for a WordPress site to protect against traffic spikes and potential overloads.

Instructions

Toggle edge cache defensive mode for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
enabledYes

Implementation Reference

  • tools/cache.js:55-57 (handler)
    The handler for the 'pressable_toggle_edge_cache_defensive_mode' tool which sends a POST request to enable or disable defensive mode for a site.
    handler: async (args) => {
    return await api.post(`/sites/${args.id}/edge-cache/defensive-mode`, { enabled: args.enabled });
}
  • tools/cache.js:47-54 (schema)
    The input schema definition for the 'pressable_toggle_edge_cache_defensive_mode' tool.
    inputSchema: {
    type: 'object',
    properties: {
        id: { type: 'string' },
        enabled: { type: 'boolean' }
    },
    required: ['id', 'enabled']
},
  • tools/cache.js:44-58 (registration)
    The tool registration object for 'pressable_toggle_edge_cache_defensive_mode'.
    {
    name: 'pressable_toggle_edge_cache_defensive_mode',
    description: 'Toggle edge cache defensive mode for a site.',
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            enabled: { type: 'boolean' }
        },
        required: ['id', 'enabled']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/edge-cache/defensive-mode`, { enabled: args.enabled });
    }
}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, whether it's reversible, what 'defensive mode' means, or any implications for the site's caching. This is a significant gap for a mutation tool.

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?

The description is concise, a single sentence with no fluff. However, it is under-specified, which borders on under-specification rather than effective conciseness, but it does not contain tautology or unnecessary words.

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

Completeness2/5

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

Given the simplicity of the tool and lack of output schema, the description should at least mention the effect of enabling/disabling defensive mode or the expected outcome. It is incomplete for an agent to understand the tool's behavior or when to invoke it.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate. It does not explain what 'id' refers to (likely site ID) or how the 'enabled' boolean maps to the toggle action. The description provides no additional meaning beyond the raw parameter names and types.

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?

The description clearly states the action: 'Toggle edge cache defensive mode for a site.' This specifies the verb (toggle), the resource (edge cache defensive mode), and the scope (for a site), which distinguishes it from sibling tools like pressable_toggle_edge_cache or pressable_purge_edge_cache.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any mention of prerequisites, exclusions, or comparison with sibling tools like toggle_edge_cache or purge_edge_cache.

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