Skip to main content
Glama

legal_put_accessibility

Configures a self-hosted WordPress accessibility panel: set launcher options, enable tools or markup repairs, and return stored settings without third-party requests.

Instructions

Configure the self-hosted accessibility tool (replaces the Ally widget; no third-party request, needs no consent). Merges: omitted keys keep their value. Switching enabled rewrites a generated Datenschutz (section Barrierefreiheits-Werkzeug). Returns the stored settings. Requires cvrt-legal 0.8.0+.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "legal_put_accessibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
colorNoLauncher colour, #rrggbb (default #1d4ed8)
toolsNoPanel tool => on/off, merged (omitted tools keep their value). Keys: bigger-text, bigger-line-height, text-align, readable-font, grayscale, contrast, highlight-links, focus-outline, reading-mask, hide-images, pause-animations, page-structure, sitemap. All on by default except sitemap. See available_tools in legal_get_accessibility
enabledNoShow the accessibility panel (default off)
repairsNoMarkup repair rule => on/off, merged (omitted rules keep their value; all off by default). cvrt-legal 0.9.0+. Keys: link-names, image-alt, iframe-title, form-labels, skip-link, lang, zoom, new-tab, duplicate-ids. Server-side, works with or without the panel, never invents or overwrites; duplicate-ids only reports. See available_repairs in legal_get_accessibility
positionNoLauncher position, default bottom-right
sitemap_urlNohttps URL for the Sitemap tool; empty = /wp-sitemap.xml
statement_urlNohttps URL of an external statement; the page wins
statement_pageNoPage id of the accessibility statement; 0 = none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv3.14.0
    • changedInput schema / properties / color / description
      Previous value: -"Launcher colour, #rrggbb"New value: +"Launcher colour, #rrggbb (default #1d4ed8)"
    • addedInput schema / properties / enabled / description
      Added value: +"Show the accessibility panel (default off)"
    • addedInput schema / properties / position / description
      Added value: +"Launcher position, default bottom-right"
    • removedInput schema / properties / repairs / $ref
      Removed value: -"#/properties/tools"
    • addedInput schema / properties / repairs / additionalProperties
      Added value: +false
    • changedInput schema / properties / repairs / description
      Previous value: -"Markup repair rule => on/off (cvrt-legal 0.9.0+): link-names, image-alt, iframe-title, form-labels, skip-link, lang, zoom, new-tab, duplicate-ids. Server-side, never invents or overwrites; see available_repairs"New value: +"Markup repair rule => on/off, merged (omitted rules keep their value; all off by default). cvrt-legal 0.9.0+. Keys: link-names, image-alt, iframe-title, form-labels, skip-link, lang, zoom, new-tab, duplicate-ids. Server-side, works with or without the panel, never invents or overwrites; duplicate-ids only reports. See available_repairs in legal_get_accessibility"
    • addedInput schema / properties / repairs / properties
      Added value: +{
      +  "duplicate-ids": {
      +    "type": "boolean"
      +  },
      +  "form-labels": {
      +    "type": "boolean"
      +  },
      +  "iframe-title": {
      +    "type": "boolean"
      +  },
      +  "image-alt": {
      +    "type": "boolean"
      +  },
      +  "lang": {
      +    "type": "boolean"
      +  },
      +  "link-names": {
      +    "type": "boolean"
      +  },
      +  "new-tab": {
      +    "type": "boolean"
      +  },
      +  "skip-link": {
      +    "type": "boolean"
      +  },
      +  "zoom": {
      +    "type": "boolean"
      +  }
      +}
    • addedInput schema / properties / repairs / type
      Added value: +"object"
    • changedInput schema / properties / tools / additionalProperties
      Previous value: -{
      -  "type": "boolean"
      -}New value: +false
    • changedInput schema / properties / tools / description
      Previous value: -"tool key => on/off (see available_tools in legal_get_accessibility)"New value: +"Panel tool => on/off, merged (omitted tools keep their value). Keys: bigger-text, bigger-line-height, text-align, readable-font, grayscale, contrast, highlight-links, focus-outline, reading-mask, hide-images, pause-animations, page-structure, sitemap. All on by default except sitemap. See available_tools in legal_get_accessibility"
    • addedInput schema / properties / tools / properties
      Added value: +{
      +  "bigger-line-height": {
      +    "type": "boolean"
      +  },
      +  "bigger-text": {
      +    "type": "boolean"
      +  },
      +  "contrast": {
      +    "type": "boolean"
      +  },
      +  "focus-outline": {
      +    "type": "boolean"
      +  },
      +  "grayscale": {
      +    "type": "boolean"
      +  },
      +  "hide-images": {
      +    "type": "boolean"
      +  },
      +  "highlight-links": {
      +    "type": "boolean"
      +  },
      +  "page-structure": {
      +    "type": "boolean"
      +  },
      +  "pause-animations": {
      +    "type": "boolean"
      +  },
      +  "readable-font": {
      +    "type": "boolean"
      +  },
      +  "reading-mask": {
      +    "type": "boolean"
      +  },
      +  "sitemap": {
      +    "type": "boolean"
      +  },
      +  "text-align": {
      +    "type": "boolean"
      +  }
      +}
  2. Addedv3.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses merge semantics ('omitted keys keep their value'), an otherwise invisible side effect ('Switching enabled rewrites a generated Datenschutz (section Barrierefreiheits-Werkzeug)'), the return value, and the version prerequisite. It still omits permission/auth requirements and what happens to the panel or statement on disable.

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?

Four compact sentences, front-loaded with the purpose before the merge and side-effect details. The parentheticals earn their place by explaining the Ally replacement and the consent implication, though the version note could be folded more tightly.

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

Completeness4/5

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

For a 9-parameter mutation tool with nested objects, no annotations and no output schema, the description covers return values ('Returns the stored settings'), merge semantics, a hidden side effect and a version gate. Remaining gaps are permission requirements and behavior when settings are disabled or cleared.

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?

Schema description coverage is 100%, so the nested tools/repairs key lists, defaults and enum are already documented. The description reinforces the merge behavior for omitted keys, which the schema also states, but adds little parameter meaning beyond that. Baseline 3 applies.

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?

States a specific verb ('Configure') and resource ('the self-hosted accessibility tool'), and the parenthetical 'replaces the Ally widget; no third-party request, needs no consent' pins down exactly which subsystem is being written to. It contrasts implicitly with the get-side siblings (legal_get_accessibility) through the configure/merge framing, though it never names an alternative explicitly.

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?

Usage context is implied rather than spelled out: the description says what the tool is for and gives a prerequisite ('Requires cvrt-legal 0.8.0+'), but never says when to prefer it over legal_put_theme or to read first with legal_get_accessibility. There are no explicit when-not conditions.

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