Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_set_php_filesystem_permissions

Configure PHP file system permissions for a WordPress site to manage access control and security settings.

Instructions

Set PHP file system permissions for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/sites.js:149-159 (handler)
    The definition and handler implementation for 'pressable_set_php_filesystem_permissions' tool.
        name: 'pressable_set_php_filesystem_permissions',
    description: 'Set PHP file system permissions for a site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/php-permissions`);
    }
},

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It identifies this is a mutation ('Set') but discloses nothing about safety implications, reversibility, what permissions values are valid, or side effects of changing filesystem permissions on a live site.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief at one sentence. While not verbose, it is underspecified rather than efficiently concise. It front-loads the action but lacks supporting details that would earn additional sentences for a security-sensitive filesystem 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?

For a tool modifying filesystem permissions (a security-critical operation), the description is inadequate given zero schema descriptions and no annotations. It fails to explain what permissions are being set, valid values, the impact on site operation, or expected behavior.

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 coverage is 0% - the 'id' parameter has no description. The phrase 'for a site' strongly implies the id refers to a site identifier, which adds minimal context, but it does not document the parameter format, how to obtain it, or that it is required (though schema shows this structurally).

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?

States a specific verb ('Set') and resource ('PHP file system permissions') and scope ('for a site'). It distinguishes from sibling 'pressable_set_php_version' by focusing on filesystem permissions rather than version configuration. However, 'PHP file system permissions' is slightly ambiguous regarding what specific permissions are being controlled.

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, prerequisites (e.g., needing specific privileges), or when not to use it. Siblings like 'pressable_update_site' might also affect site settings, but no differentiation is provided.

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