Skip to main content
Glama

mysql_current_site

Retrieve details about the currently connected Local WordPress site, including its selection method. Use this to confirm the active site for development and analysis.

Instructions

Get information about the currently connected Local WordPress site, including how it was selected

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the mysql_current_site tool. Returns information about the currently connected Local WordPress site, including site name, ID, path, domain, selection method, socket path, and port.
    case 'mysql_current_site': {
      if (!currentSiteSelection) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(
                {
                  error: 'No site selection information available',
                  note: 'Using environment variables or default configuration',
                },
                null,
                2
              ),
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                siteName: currentSiteSelection.siteName,
                siteId: currentSiteSelection.siteInfo.siteId,
                sitePath: currentSiteSelection.sitePath,
                domain: currentSiteSelection.domain,
                selectionMethod: currentSiteSelection.selectionMethod,
                socketPath: currentSiteSelection.siteInfo.socketPath,
                port: currentSiteSelection.siteInfo.port,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Schema definition for mysql_current_site tool. No input parameters required.
    {
      name: 'mysql_current_site',
      description:
        'Get information about the currently connected Local WordPress site, including how it was selected',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:157-161 (registration)
    Registration of tools includes mysql_current_site via the ListToolsRequestSchema handler that returns the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
  • Module-level state variable that stores the current site selection, populated at startup by getLocalMySQLConfig and used by the mysql_current_site handler.
    // Store site selection for the mysql_current_site tool
    let currentSiteSelection: SiteSelectionResult | undefined;
  • This function performs site selection (via selectSite()) and returns the connection config with an embedded _siteSelection property. The _siteSelection is extracted at startup in index.ts and stored in currentSiteSelection for use by the mysql_current_site tool handler.
    export function getLocalMySQLConfig(database?: string): {
      host?: string;
      port?: number;
      user: string;
      password: string;
      database?: string;
      socketPath?: string;
      multipleStatements?: boolean;
      timezone?: string;
      _siteSelection?: SiteSelectionResult;
    } {
      const selection = selectSite();
    
      debugLog(`Selected site: ${selection.siteName} via ${selection.selectionMethod}`);
      debugLog(`  Path: ${selection.sitePath}`);
      debugLog(`  Domain: ${selection.domain}`);
      debugLog(`  Socket: ${selection.siteInfo.socketPath}`);
    
      return {
        socketPath: selection.siteInfo.socketPath,
        user: 'root',
        password: 'root',
        database: database || 'local',
        multipleStatements: false,
        timezone: 'Z',
        _siteSelection: selection,
      };
    }
Behavior2/5

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

No annotations are provided, so the description must carry behavioral transparency. It does not disclose read-only nature, side effects, or auth requirements beyond basic purpose, leaving gaps for a tool that likely performs a safe query.

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 description is a single, front-loaded sentence with no extraneous words, effectively conveying the tool's purpose.

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

Completeness5/5

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

Given the tool has no parameters, no output schema, and a simple purpose, the description fully explains what it does and what it returns (information and selection method), making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters and 100% coverage, so the baseline is 4. The description does not need to add parameter semantics as none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves information about the currently connected Local WordPress site, including selection method, which distinguishes it from sibling tools like mysql_list_sites, mysql_query, and mysql_schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (when needing current site info) but does not explicitly exclude alternatives or provide when-not scenarios; context is clear enough given sibling differentiation.

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/verygoodplugins/mcp-local-wp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server