Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

  • tools/cache.js:39-42 (handler)
    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}`);
    }
},

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, but it only states the action. It does not reveal side effects, reversibility, permission requirements, or return behavior, which is critical for a state-changing toggle operation.

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 description is a single sentence with no wasted words, immediately conveying the core action. It is optimally concise and front-loaded, earning a perfect score for this dimension.

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 lack of annotations and output schema, the description is incomplete. It provides no information about return values, side effects, or how the site is identified beyond the implicit 'id' parameter. The tool's simplicity is acknowledged, but the description still leaves substantial gaps for an agent.

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%, and the description does not adequately compensate. While 'enable or disable' hints at the 'enabled' boolean and 'for a site' implies the 'id' parameter, it does not explicitly explain their roles or expected values, leaving the agent to infer semantics.

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 clearly states the verb 'Enable or disable' and the resource 'edge caching for a site', making the action unambiguous. However, it does not distinguish this from sibling tools like pressable_toggle_edge_cache_defensive_mode or pressable_purge_edge_cache, so it falls short of a perfect score.

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 does not mention prerequisites, exclusions, or relationships with sibling tools such as pressable_get_edge_cache_status or pressable_purge_edge_cache, leaving the agent without context for selection.

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