Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

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

  • 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 });
    }
  • 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 });
        }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to explain what defensive mode does, what happens when enabled/disabled, whether changes are immediate, or any side effects on site performance.

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 single sentence is efficient with no redundant words, but its extreme breverity contributes to underspecification given the lack of schema documentation.

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?

With zero schema descriptions, no annotations, and no output schema, the description provides insufficient context for an AI to understand 'defensive mode' behavior or parameter requirements. Needs elaboration on the feature's purpose and parameter details.

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?

Schema description coverage is 0%, requiring the description to compensate. While 'for a site' implicitly indicates the 'id' parameter refers to a site ID, the 'enabled' boolean parameter is completely undocumented with no explanation of true vs false semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Toggle') and resource ('edge cache defensive mode') but fails to define what 'defensive mode' entails or distinguish this from the sibling 'pressable_toggle_edge_cache' tool. It adds minimal information beyond the tool name itself.

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

Usage Guidelines1/5

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

Provides no guidance on when to use this tool versus alternatives like 'pressable_toggle_edge_cache' or 'pressable_get_edge_cache_status'. No prerequisites, side effects, or conditions for use are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PCWProps/pressable-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server