Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_set_site_usage_limits

Configure storage limits for WordPress site filesystems or databases to manage resource usage and prevent overages.

Instructions

Set filesystem or database usage limits for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
typeYes
limitYesLimit in bytes
warning_headroomNoWarning headroom in bytes

Implementation Reference

  • The handler function for 'pressable_set_site_usage_limits' which updates site usage limits via the API.
    handler: async (args) => {
        const { id, type, ...data } = args;
        return await api.put(`/sites/${id}/usage/${type}`, data);
    }
  • The input schema defining the parameters for 'pressable_set_site_usage_limits'.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            type: { type: 'string', enum: ['filesystem', 'database'] },
            limit: { type: 'integer', description: 'Limit in bytes' },
            warning_headroom: { type: 'integer', description: 'Warning headroom in bytes' }
        },
        required: ['id', 'type', 'limit']
    },
  • tools/usage.js:29-46 (registration)
    The registration object for 'pressable_set_site_usage_limits' within the usageTools array.
            name: 'pressable_set_site_usage_limits',
            description: 'Set filesystem or database usage limits for a site.',
            inputSchema: {
                type: 'object',
                properties: {
                    id: { type: 'string' },
                    type: { type: 'string', enum: ['filesystem', 'database'] },
                    limit: { type: 'integer', description: 'Limit in bytes' },
                    warning_headroom: { type: 'integer', description: 'Warning headroom in bytes' }
                },
                required: ['id', 'type', 'limit']
            },
            handler: async (args) => {
                const { id, type, ...data } = args;
                return await api.put(`/sites/${id}/usage/${type}`, data);
            }
        }
    ];
Behavior2/5

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

No annotations provided, so description carries full burden. States the configuration action but omits critical behavioral details: whether limits are hard caps or soft quotas, what happens when exceeded (data rejection vs warnings), and whether changes are immediately enforced or require propagation.

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

Conciseness4/5

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

Single sentence with no redundancy and appropriate length. Front-loaded with action and target. However, extreme brevity sacrifices necessary behavioral context for a limits-configuration tool.

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?

Inadequate for a 4-parameter mutation tool with zero annotations and no output schema. Missing: parameter formats (is id numeric or slug?), side effects of limit enforcement, and return value description.

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 50%. Description adds semantic context for the 'type' parameter ('filesystem or database') and implies 'id' refers to a site, but fails to explicitly document the 'id' parameter or clarify the relationship between 'limit' and 'warning_headroom' values.

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?

Clear verb 'Set' with specific resources 'filesystem or database usage limits' and scope 'for a site'. Distinguishes from sibling get_site_usage by specifying the write action, though could further differentiate from other configuration tools like set_php_version.

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 on when to use versus alternatives (e.g., get_site_usage to check current consumption), no prerequisites mentioned, and no warning about potential service impact when lowering limits.

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