Skip to main content
Glama

site_overview

Read-only

Get a WordPress health snapshot in one call: see core version, pending updates, installed plugins, and themes to assess maintenance needs.

Instructions

One-call health snapshot: WordPress version, pending updates, plugins and themes.

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": "site_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing that the call aggregates version, updates, plugins and themes in one round trip ('one-call'), but says nothing about authentication, permissions, cost, or result shape.

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?

A single front-loaded sentence with a colon-delimited list; nothing is wasted. The terseness is efficient, though it leaves little room for the routing and parameter context an agent needs.

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?

For a simple, zero-required-parameter read tool with no output schema, the description adequately conveys what comes back. It falls short on the one thing not covered by structured data: the meaning of the 'site' argument and how this differs from the sibling health-check tool.

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?

There is one optional parameter, 'site', with zero schema description coverage and a null default, yet the description never mentions it. It does not explain whether null means the current/default site or what identifier format is accepted, so the only ambiguous input is left entirely undocumented.

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?

The description names a concrete resource and enumerates exactly what the snapshot contains: WordPress version, pending updates, plugins and themes. It is clear this is an aggregated read, though the phrase 'health snapshot' partially overlaps with the sibling check_site_health without clarifying the boundary.

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?

There is no explicit statement of when to call this versus check_site_health or the wp / wp_commands tools, which are close neighbors. The word 'snapshot' implies a quick overview use case, but the agent must infer that.

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