Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_mu_plugin

Retrieve details for a specific must-use WordPress plugin by providing its ID, enabling management of site functionality through the Pressable API.

Instructions

Get details for a specific MU plugin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for 'pressable_get_mu_plugin' that fetches plugin details from the API.
    handler: async (args) => {
        return await api.get(`/mu-plugins/${args.id}`);
    }
  • Input schema for 'pressable_get_mu_plugin' defining the required 'id' parameter.
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'integer' } },
        required: ['id']
    },
  • Registration block for the 'pressable_get_mu_plugin' tool.
        {
            name: 'pressable_get_mu_plugin',
            description: 'Get details for a specific MU plugin.',
            inputSchema: {
                type: 'object',
                properties: { id: { type: 'integer' } },
                required: ['id']
            },
            handler: async (args) => {
                return await api.get(`/mu-plugins/${args.id}`);
            }
        }
    ];
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 details' implies a read operation, it omits safety confirmations, permission requirements, rate limits, and what constitutes 'details' in the response.

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 waste, front-loaded with the action and target. However, extreme brevity leaves critical information gaps.

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 tool with 0% schema coverage and no annotations. The description covers only the high-level purpose, failing to document the mandatory ID parameter or behavioral constraints expected for API consumption.

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% (parameter 'id' undocumented) and the description fails to compensate by explaining what the ID represents, its format, or how to obtain it. The word 'specific' weakly implies an identifier is 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?

States the basic operation (Get details) and resource (MU plugin) but lacks scope differentiation from sibling 'pressable_list_mu_plugins'. The phrase 'specific' hints at single-item retrieval but does not explicitly contrast with listing operations.

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 alternatives (e.g., pressable_list_mu_plugins to discover IDs), prerequisites for the ID parameter, or error conditions.

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