Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp

Change how the accessibility widget looks and which profiles it offers

set_widget_appearance
DestructiveIdempotent

Use this when the user wants the Inclusify widget on their site to look different — match brand colour, move it off something it covers, change its size or icon — or to change which accessibility PROFILES it offers visitors. WRITES to this website's Inclusify configuration, never to the site's code or theme: it changes what the widget bundle renders. Takes effect within about a minute; the edge cache is purged as part of the change. Every setting is optional and anything you leave out is left exactly as it is, so you can change one without knowing the others. This REQUIRES CONFIRMATION — call without "confirm" first, show the user the preview, then call again with the token once they agree — because the result is visible to that site's real visitors. Removing an accessibility profile is the consequential part: it takes an accommodation away from visitors who may be relying on it, so the preview names each one. Note that "enabledProfiles" is a COMPLETE REPLACEMENT LIST, not an addition — whatever you pass becomes the whole set, so include the ones already on that should stay on. The account owner is emailed a record with a link to undo it. Needs the STARTER plan or above, matching the panel. Shopify-billed stores cannot use this at all — they customise the widget from the Shopify app. To turn the widget off entirely, use set_widget_enabled instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoLeave this out on the first call to get a preview of exactly what would change, plus a confirmation token. Call again with the same arguments and that token to apply the change. The token lasts 10 minutes and works once.
websiteYesThe website domain as registered in Inclusify, e.g. "example.com".
languageNoWidget interface language. Anything other than English needs a plan with more than one language.
positionNoWhich corner the widget button sits in.
triggerIconNoWhich icon the button shows.
triggerSizeNoButton size in pixels, 40 to 80.
primaryColorNoSix-digit hex, e.g. "#0066ff". The widget button and accents use it.
showOnMobileNoWhether the widget appears on small screens.
enabledProfilesNoThe accessibility profiles offered to visitors, as a complete replacement list — whatever you pass becomes the whole set, so include the ones already on that should stay on. Removing one takes that accommodation away from visitors using it.
triggerElementIdNoThe id of an element on the CUSTOMER'S OWN site that opens the widget — usually a footer or menu link they have styled themselves, e.g. "footer-accessibility". On every page where that element exists the floating button is not rendered, so their link becomes the only visible way in; on pages where it is missing the floating button comes back, so the widget is never unreachable. An element id, NOT a CSS selector, and without the leading "#". Pass null to remove it and go back to the floating button. Setting this does not put the element on their site — they add the id to their own theme; if you have not confirmed the element exists, say so rather than assuming.
hideForeverEnabledNoWhether visitors get a "don't show again" option. Needs the plan that includes it.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, and the description enriches this substantially: it writes to Inclusify configuration, not site code/theme, purges the edge cache, takes effect in about a minute, emails the account owner an undo link, and being visible to real visitors is why confirmation is required. This goes well beyond annotation defaults without contradicting them.

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?

Although long, every sentence carries operational weight: when to use, confirmation flow, replacement-list semantics, plan constraints, Shopify exclusion, and alternative tool routing. The front-loaded 'Use this when...' framing lets an agent quickly decide applicability before reading deeper.

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 an 11-parameter mutation tool with no output schema and high-stakes destructive potential, the description is remarkably complete. It covers prerequisites, side effects, confirmation steps, undo path, scope of changes, plan restrictions, and what not to assume about triggerElementId. Together with the fully covered schema, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the schema already documents every parameter. The description adds real extra meaning beyond the schema by warning that enabledProfiles is a COMPLETE REPLACEMENT LIST and by explaining that removing a profile takes an accommodation away from visitors. It also clarifies the confirm parameter workflow without restating the schema's token details.

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 opens with a specific use case ('user wants the Inclusify widget on their site to look different') and names the exact dimensions it covers: brand color, position, size, icon, and accessibility profiles. It clearly differentiates from the sibling tool set_widget_enabled by explicitly saying to use that tool 'to turn the widget off entirely.'

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

Usage Guidelines5/5

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

It states exactly when to use this tool, when not to (Shopify-billed stores must use the Shopify app), and which alternative to use for disabling the widget entirely. It also provides the required confirmation workflow, plan requirements, and the behavior of leaving optional parameters unchanged.

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

All Inclusify Accessibility toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

The descriptions do exceptional cross-referencing work, explicitly separating near-neighbor pairs (add_website vs add_domain, list_alt_findings vs check_page_alt_text, plan_options vs billing_link, widget_status vs widget_usage). A few clusters remain that an agent could confuse without reading carefully, notably site_overview vs compliance_status (both report statement existence and scan-record state) and crawl_summary vs list_monitored_pages vs site_overview (all touch coverage numbers). Overall, distinct purposes are clearly delineated despite the large surface.

Naming Consistency4/5

All names are lowercase snake_case with strong family patterns: list_* (5 tools), add_* (3), set_* (7), plus org_* and *_history pairs. The main inconsistency is the mix of verb-led names (list_violations, set_slack_channel, start_crawl) with noun-led read names (site_overview, compliance_status, widget_usage, next_steps), but the noun-led names follow a coherent 'what it returns' vocabulary (status, summary, history, overview, rollup). Minor deviations rather than chaos.

Tool Count3/5

36 tools is heavy and sits above the 25-tool threshold where agent navigation starts to degrade, but the server covers a genuinely broad domain: website lifecycle, monitoring, four finding types, four live-audit tools, seven config setters, org rollups, billing, and CI. Most tools earn their place and none are duplicates, but several could plausibly be merged (set_slack_channel/set_slack_events/set_monitoring_settings into one notifications tool; list_violations/list_alt_findings/list_content_findings with a filter). The count is on the edge of unwieldy for an agent's tool-selection step.

Completeness3/5

The read/audit/analysis side is rich and well-covered: findings, history, live checks, org rollups, coverage, and validation all have tools. However, the write side is one-directional: add_monitored_pages is explicitly add-only, and there is no remove_website, remove_domain, or remove_monitored_pages, so teardown and 'stop monitoring this page' requests hit dead ends that the descriptions acknowledge belong to the panel. Statement content writing and widget installation are also panel/browser-only by design, which is documented but still leaves those operations outside the agent's reach.

Resources