Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_get_site_metrics

Retrieve performance metrics for a WordPress site to monitor speed, uptime, and resource usage. Provide the site ID to access detailed analytics.

Instructions

Get performance metrics for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/usage.js:12-14 (handler)
    The handler for pressable_get_site_metrics executes an API GET request to fetch site metrics.
    handler: async (args) => {
    return await api.get(`/sites/${args.id}/metrics`);
}
  • tools/usage.js:7-11 (schema)
    The input schema for pressable_get_site_metrics requiring a site 'id'.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string' } },
    required: ['id']
},
  • tools/usage.js:4-15 (registration)
    The tool definition and registration for pressable_get_site_metrics.
    {
    name: 'pressable_get_site_metrics',
    description: 'Get performance metrics for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/metrics`);
    }
},

Tool Definition Quality

C2.6/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. While 'Get' implies read-only safety, it fails to disclose what metrics are returned (CPU, bandwidth, response time?), response format, caching behavior, or rate limits.

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?

Single sentence is appropriately front-loaded and non-redundant, but given the lack of schema descriptions and annotations, this brevity represents 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?

With no output schema, no annotations, and 0% schema parameter coverage, the description should elaborate on return values and parameter details. 'Performance metrics' remains undefined and the ID parameter is not explicitly mentioned.

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% (id parameter undocumented). Description implicitly indicates the id refers to a site ('for a specific site'), but provides no details on ID format, constraints, or whether it accepts slugs vs UUIDs. Minimal compensation for schema deficiency.

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 clear verb ('Get') and resource ('performance metrics') with scope ('for a specific site'). Distinguishes reasonably from siblings like pressable_get_site (general details) and pressable_get_site_usage (usage limits), though could be more explicit about what 'performance' encompasses.

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 versus pressable_get_site_usage or pressable_get_site. No mention of prerequisites (site must exist) or timing (real-time vs cached metrics).

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