Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_get_edge_cache_status

Check edge caching status for a WordPress site to verify content delivery performance and troubleshoot caching issues.

Instructions

Get the status of edge caching for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSite ID or name

Implementation Reference

  • tools/cache.js:12-14 (handler)
    The handler function for 'pressable_get_edge_cache_status' which performs a GET request to the site's edge cache endpoint.
    handler: async (args) => {
    return await api.get(`/sites/${args.id}/edge-cache`);
}
  • tools/cache.js:7-11 (schema)
    The input schema for 'pressable_get_edge_cache_status' requiring a site id.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string', description: 'Site ID or name' } },
    required: ['id']
},
  • tools/cache.js:4-15 (registration)
    The full tool definition/registration for 'pressable_get_edge_cache_status' in tools/cache.js.
    {
    name: 'pressable_get_edge_cache_status',
    description: 'Get the status of edge caching for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string', description: 'Site ID or name' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/edge-cache`);
    }
},

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. States 'Get the status' implying read-only behavior but does not disclose what the status includes (enabled/disabled state, metrics, etc.), whether the operation is idempotent, or potential error conditions. Minimal behavioral disclosure for a tool with no safety annotations.

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?

Single sentence of 9 words. Information-dense with no filler. Appropriately front-loaded with the action and target resource immediately clear.

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

Completeness3/5

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

Sufficient for a simple single-parameter read operation with complete schema coverage. However, lacks return value description (no output schema exists to compensate), leaving ambiguity about what 'status' encompasses. Adequate but has clear gaps regarding response structure.

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?

Schema coverage is 100% with the 'id' parameter fully documented as 'Site ID or name'. Description mentions 'for a specific site' which aligns with the schema but adds no additional semantic value (syntax examples, format constraints, identification logic) beyond the schema definition. Baseline score applies.

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?

Uses specific verb 'Get' and resource 'status of edge caching for a specific site'. Clearly identifies the scope (site-specific) and operation (retrieval). Lacks explicit differentiation from siblings like 'pressable_toggle_edge_cache' or 'pressable_purge_edge_cache', though the verb choice implicitly distinguishes them.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to check status vs. purge cache). No mention of prerequisites, rate limits, or typical use cases.

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