Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_set_php_version

Change the PHP version for a WordPress site hosted on Pressable. Specify the site ID and desired PHP version (8.0, 8.1, 8.2, or 8.3) to update the server configuration.

Instructions

Set the PHP version for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
php_versionYes

Implementation Reference

  • Handler function for pressable_set_php_version, which makes a POST request to update the site's PHP version.
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/php-version`, { php_version: args.php_version });
    }
  • Input schema defining the required parameters (id, php_version) for pressable_set_php_version.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            php_version: { type: 'string', enum: ['8.0', '8.1', '8.2', '8.3'] }
        },
        required: ['id', 'php_version']
    },
  • tools/server.js:28-42 (registration)
    Tool registration for pressable_set_php_version in tools/server.js.
    {
        name: 'pressable_set_php_version',
        description: 'Set the PHP version for a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                php_version: { type: 'string', enum: ['8.0', '8.1', '8.2', '8.3'] }
            },
            required: ['id', 'php_version']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/php-version`, { php_version: args.php_version });
        }
    },
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 but fails to mention critical mutation traits: whether this causes downtime, requires a server restart, is idempotent, or what happens if an invalid transition is attempted.

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 appropriately front-loaded with the action verb, contains zero redundant words, and efficiently conveys the core purpose without wasting tokens.

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?

For a configuration mutation tool with zero schema descriptions, no annotations, and no output schema, the description is insufficient. It omits operational details (downtime warnings, async vs sync behavior) and return value information that would be necessary for safe agent operation.

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 by implicitly mapping 'PHP version' to the php_version parameter and 'specific site' to the id parameter. However, it does not explicitly confirm that 'id' refers to the site identifier or describe the expected format (UUID, numeric, etc.).

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 action ('Set'), the resource ('PHP version'), and the scope ('for a specific site'). It effectively distinguishes from sibling tools like pressable_set_php_filesystem_permissions and pressable_set_site_usage_limits by specifying the exact configuration being modified.

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., pressable_update_site), nor does it state prerequisites such as site existence requirements or permissions needed to modify PHP versions.

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