Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_list_security_alerts

Retrieve security alerts for plugins and themes across WordPress sites to monitor vulnerabilities and maintain site protection.

Instructions

Get security alerts for plugins and themes across all sites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType of alerts to retrieve

Implementation Reference

  • The handler function for 'pressable_list_security_alerts' which fetches security alerts from the API.
    handler: async (args) => {
        const type = args.type || 'plugin';
        return await api.get(`/security-alerts/${type}s`);
    }
  • Input schema validation for 'pressable_list_security_alerts'.
    inputSchema: {
        type: 'object',
        properties: {
            type: { type: 'string', enum: ['plugin', 'theme'], description: 'Type of alerts to retrieve' }
        }
    },
  • tools/security.js:4-17 (registration)
    Registration of the 'pressable_list_security_alerts' tool.
    {
        name: 'pressable_list_security_alerts',
        description: 'Get security alerts for plugins and themes across all sites.',
        inputSchema: {
            type: 'object',
            properties: {
                type: { type: 'string', enum: ['plugin', 'theme'], description: 'Type of alerts to retrieve' }
            }
        },
        handler: async (args) => {
            const type = args.type || 'plugin';
            return await api.get(`/security-alerts/${type}s`);
        }
    }
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. It fails to explain what constitutes a 'security alert' (vulnerabilities, outdated versions, malware), whether data is real-time or cached, or any permission requirements specific to security data.

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 description is appropriately sized with zero waste. It is front-loaded with the action verb and efficiently combines resource type, filter scope, and spatial scope ('across all sites') into a compact statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple parameter structure (1 optional parameter, 100% schema coverage, no nested objects) and lack of output schema, the description adequately covers the basic function. However, for a security-related endpoint, it is incomplete—it should describe what constitutes a security alert or link to the vulnerability criteria used.

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 100% (the 'type' parameter is fully described in the schema), establishing a baseline of 3. The description mentions 'plugins and themes' which aligns with the enum values but adds no additional semantic detail about parameter usage, validation, or defaults beyond what the schema already provides.

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 uses a clear verb ('Get') and specific resource ('security alerts'), and distinguishes itself from sibling tools like 'pressable_list_plugins' by specifying the security context. The scope 'across all sites' adds useful clarification.

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?

There is no guidance on when to use this tool versus alternatives, or what conditions warrant checking security alerts. The 'across all sites' scope is mentioned but not contrasted with potential site-specific filtering options.

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