Skip to main content
Glama
Sign In
WordPress MCP Server

WordPress MCP Server

by c-sakel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Prüfe Farbkontrast

a11y_check_color_contrast

Analyze color contrast in WordPress content to ensure WCAG compliance. Identifies contrast fails and guides fixes for accessible design.

Instructions

Analysiert die verwendeten Farben auf WCAG-Konformität

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

Input Schema

NameRequiredDescriptionDefault
postIdNoPost/Page ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the analysis purpose; it does not mention that it's a read-only operation, describe what the output looks like, or address any side effects or prerequisites.

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?

A single, efficient sentence that front-loads the core purpose without unnecessary words.

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?

The description is adequate for a simple check tool but lacks details about return format, scope, or usage context. Without an output schema or annotations, it should provide more context on what the user will receive.

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 input schema has 100% description coverage for its single optional parameter (postId), so the baseline is 3. The description adds no extra parameter context, but the schema already documents the parameter adequately.

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's function with a specific verb ('Analysiert') and resource ('Farben') tied to WCAG compliance, distinguishing it from sibling a11y checkers like a11y_check_forms or a11y_check_images.

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 tool versus the other a11y checkers. It only states the purpose without any contextual usage instructions or alternatives.

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