Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_toggle_edge_cache

Enable or disable edge caching to control content delivery speed for a WordPress site.

Instructions

Enable or disable edge caching for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
enabledYes

Implementation Reference

  • Handler for pressable_toggle_edge_cache which enables or disables edge caching via API.
    handler: async (args) => {
        const method = args.enabled ? 'enable' : 'disable';
        return await api.post(`/sites/${args.id}/edge-cache/${method}`);
    }
  • tools/cache.js:29-43 (registration)
    Registration and definition of the pressable_toggle_edge_cache tool.
        name: 'pressable_toggle_edge_cache',
        description: 'Enable or disable edge caching for a site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                enabled: { type: 'boolean' }
            },
            required: ['id', 'enabled']
        },
        handler: async (args) => {
            const method = args.enabled ? 'enable' : 'disable';
            return await api.post(`/sites/${args.id}/edge-cache/${method}`);
        }
    },
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 mention whether this is a destructive/reversible operation, whether existing cached content is purged upon disable, or if changes propagate immediately. It only indicates that a state change occurs.

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?

The single sentence is efficiently front-loaded with the action verbs, contains zero redundancy, and every word earns its place. The brevity is appropriate for a simple toggle operation.

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 zero annotation coverage, zero schema descriptions, no output schema, and the mutation nature of the tool, the description is insufficiently complete. It lacks critical invocation details (parameter semantics, side effects, return values) necessary for safe use.

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?

With 0% schema description coverage, the description partially compensates. 'Enable or disable' semantically maps to the `enabled` boolean parameter, and 'for a site' weakly implies the `id` parameter refers to a site identifier. However, it does not explicitly confirm these mappings or document expected ID formats.

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 provides specific verbs ('Enable or disable'), a specific resource ('edge caching'), and scope ('for a site'). It inherently distinguishes from sibling tools like `pressable_get_edge_cache_status` (read vs. write) and `pressable_purge_edge_cache` (clearing cache vs. toggling the feature).

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when to purge vs. toggle), mentions no prerequisites, and does not warn about potential service interruption or propagation delays.

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