Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_phpmyadmin_url

Generate a time-limited phpMyAdmin URL to access and manage database for a specific WordPress site on Pressable hosting.

Instructions

Get a time-limited phpMyAdmin URL for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The handler function for pressable_get_phpmyadmin_url tool, which calls the Pressable API to retrieve a phpMyAdmin URL.
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/wordpress/phpmyadmin`);
    }
  • tools/sites.js:204-215 (registration)
    The registration of the pressable_get_phpmyadmin_url tool within the siteTools array.
    {
        name: 'pressable_get_phpmyadmin_url',
        description: 'Get a time-limited phpMyAdmin URL for a site.',
        inputSchema: {
            type: 'object',
            properties: { id: { type: 'string' } },
            required: ['id']
        },
        handler: async (args) => {
            return await api.get(`/sites/${args.id}/wordpress/phpmyadmin`);
        }
    }
Behavior3/5

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

Without annotations, the description carries the full disclosure burden. It successfully communicates that the URL is 'time-limited' (critical security context), but omits expiration duration, permission scope (read-only vs admin), or whether usage is audited. Just meets minimum viable disclosure.

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?

Extremely efficient single sentence (7 words) with zero redundancy. Key behavioral qualifier ('time-limited') is front-loaded. Appropriate length for a single-parameter read operation.

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 tool's simplicity (1 parameter, no output schema) and lack of annotations, the description covers the essential operation. However, for a security-sensitive database access tool, it lacks completeness regarding access scope, session duration, and revocation behavior.

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 has 0% description coverage for the required 'id' parameter. The description implies this is a site ID via the phrase 'for a site', but does not compensate for the schema gap by clarifying expected format, where to obtain it, or distinguishing it from other ID types used in sibling tools.

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?

Specific verb (Get) and resource (phpMyAdmin URL) with a key qualifier (time-limited) that distinguishes it from generic site access tools like pressable_get_site or pressable_get_backup_download_url. Would be 5 if it explicitly confirmed the ID parameter refers to a site ID.

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., direct database tools), nor mentions prerequisites like site ownership or security considerations. The 'time-limited' phrase implies temporary use but does not elaborate.

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