Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_site_usage

Retrieve storage and resource usage data for a WordPress site to monitor performance and manage capacity.

Instructions

Get storage and resource usage for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for the pressable_get_site_usage tool, which fetches site usage from the Pressable API.
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/usage`);
    }
  • tools/usage.js:17-27 (registration)
    The full registration object for the pressable_get_site_usage tool, including name, description, schema, and handler.
        name: 'pressable_get_site_usage',
        description: 'Get storage and resource usage for a specific site.',
        inputSchema: {
            type: 'object',
            properties: { id: { type: 'string' } },
            required: ['id']
        },
        handler: async (args) => {
            return await api.get(`/sites/${args.id}/usage`);
        }
    },
Behavior2/5

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

No annotations are provided, placing the full disclosure burden on the description. The text specifies 'storage and resource usage' but does not clarify what resources are included (CPU, bandwidth, disk), whether data is cached or real-time, rate limits, or the return value structure. It confirms the read operation but omits critical behavioral context.

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?

The single sentence is appropriately sized and front-loaded with the operation and resource. However, given the complete lack of schema descriptions and annotations, extreme brevity becomes under-specification rather than efficient communication.

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 resource retrieval tool with no output schema, undocumented parameters, and no annotations, the description must provide sufficient context to interpret results. It fails to explain what constitutes 'usage' data, how it relates to the sibling 'pressable_set_site_usage_limits', or what the caller will receive, leaving significant gaps.

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?

With 0% schema description coverage, the description must compensate for the undocumented 'id' parameter. While 'for a specific site' implies the ID refers to a site identifier, it does not explicitly define the parameter as 'site_id', describe acceptable formats (UUID, numeric, slug), or indicate it is the sole identifier required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool retrieves 'storage and resource usage' using the verb 'Get' and identifies the resource. However, it fails to differentiate from siblings like 'pressable_get_site' (likely general config) or 'pressable_get_site_metrics' (likely performance data), leaving ambiguity about whether this returns current consumption vs. historical statistics.

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 like 'pressable_get_site_metrics' or when retrieving site details via 'pressable_get_site'. It lacks explicit prerequisites, scope limitations, or exclusion criteria.

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