Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_php_error_logs

Retrieve PHP error logs for WordPress sites to identify and resolve issues affecting site functionality.

Instructions

Get PHP error logs for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function for the 'pressable_get_php_error_logs' tool which makes an API call to fetch PHP error logs.
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/php-error-logs`);
    }
  • tools/server.js:16-27 (registration)
    Tool registration and definition for 'pressable_get_php_error_logs'.
    {
        name: 'pressable_get_php_error_logs',
        description: 'Get PHP error logs for a site.',
        inputSchema: {
            type: 'object',
            properties: { id: { type: 'string' } },
            required: ['id']
        },
        handler: async (args) => {
            return await api.get(`/sites/${args.id}/php-error-logs`);
        }
    },
Behavior2/5

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

No annotations provided, so description bears full burden. While 'get' implies read-only, it fails to disclose whether logs are truncated, formatted as text/JSON, or if retrieval is rate-limited. No mention of potential size limits for large logs.

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 or filler. Front-loaded with the core action. However, extreme brevity contributes to 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?

Lacks output description despite no output schema being present—critical for a log retrieval tool where return format (raw text vs structured entries) is unknown. Single parameter undocumented beyond implied site reference.

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% with no parameter descriptions. Description mentions 'for a site' hinting that 'id' refers to site ID, but does not explicitly document the parameter name, format (UUID vs numeric), or that it is required.

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 specific verb (get) and resource (PHP error logs) with scope (site). Implicitly distinguishes from sibling pressable_get_account_activity_logs by specifying 'site' vs 'account' context.

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., pressable_get_site for general info), no prerequisites mentioned, and no indication of log freshness or retention 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