Skip to main content
Glama
Sign In
local-wp-mcp

local-wp-mcp

by teamchrisfromthelc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get WordPress Site Info

wp_site_info
Read-only

Retrieve detailed information about a Local by Flywheel WordPress site, including site URL, WordPress version, active theme, and PHP version.

Instructions

Get detailed information about the current Local by Flywheel WordPress site, including the site URL, WordPress version, active theme, and PHP version.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_site_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite name, ID, or domain. Uses env var if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's read-only nature is clear. The description adds transparency by specifying exactly which site details are returned, giving the agent expectation of output.

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 one well-crafted sentence that frontloads the action and resource, then lists concrete examples of returned data. No filler or redundancy.

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?

For a read-only info tool with one optional parameter and annotations covering safety, this description is complete. It clearly states the tool's purpose, what it retrieves, and the source (Local by Flywheel WordPress site), which is sufficient for an agent to select and invoke it.

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?

The single parameter 'site' is fully described in the schema ('Site name, ID, or domain. Uses env var if not specified.'). The description does not add information about parameter formatting or defaults beyond what the schema provides, so it relies on the schema.

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 uses the specific verb 'Get' and names the resource as 'detailed information about the current Local by Flywheel WordPress site', enumerating key fields (URL, version, theme, PHP). This clearly distinguishes it from sibling tools like wp_list_sites (which lists sites) and mysql_query (which queries database).

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving site details but does not explicitly state when to choose it over alternatives such as wp_cli_run or mysql_query. There is no mention of exclusions or alternative contexts, leaving room for interpretation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools