Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

obtener_configuraciones

Retrieve a WordPress site's general settings and metadata, including title, description, URL, admin email, timezone, date format, and language.

Instructions

Obtiene las configuraciones y metadatos generales del sitio web (título, descripción, URL, email administrativo, zona horaria, formato de fecha e idioma del sitio).

Returns: Resumen de las opciones configuradas en WordPress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It conveys the read-only, whole-site scope and hints at the response content ('Resumen de las opciones configuradas en WordPress'), but says nothing about permission/auth requirements or whether any settings are sensitive or restricted for lower-privileged users.

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?

Purpose is front-loaded in the first line and the field enumeration is efficient. The trailing 'Returns:' block largely restates the same content and is redundant given that an output schema already exists.

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 zero-arg read tool with an output schema, little explanation is required, and the description covers scope and returned fields. However, it leaves out the operational context that would matter here — who may call it and whether the returned admin email/timezone data is safe to surface — and duplicates the output schema rather than adding to it.

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 tool takes zero parameters, which sets the baseline at 4. The description correctly makes no parameter claims and focuses on scope, so nothing is needed to interpret the empty input 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?

States a specific verb ('Obtiene') and resource ('configuraciones y metadatos generales del sitio web') and then enumerates the exact fields returned (título, descripción, URL, email administrativo, zona horaria, formato de fecha, idioma). The read-only intent is unmistakable next to the sibling 'actualizar_configuracion', so an agent can select it without opening the schema.

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?

The text only describes what comes back; it never says when to call this tool, when not to, or what alternative to prefer. There are no prerequisites or sequencing hints (e.g., call before updating settings or before publishing).

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