Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp
OverviewDiscussionsAdmin

Whether the accessibility widget is actually on the site

widget_status
Read-only

Use this when the question is about the widget itself rather than about accessibility findings: 'is the widget working', 'is it installed', 'why can't I see it', 'did the install work', 'how do I add it', 'is it live for visitors'. Answers with two separate facts that are commonly mistaken for one — whether widget serving is enabled on the Inclusify account (a setting that defaults to ON for every account before anything is installed, so on its own it proves nothing), and whether the widget has EVER been seen on the site — a report from the embed on one of the site's own pages, or a daily monitoring scan that watched it run — which is the only evidence that it is really there. Never report the enabled flag as installation. A site with several domains is answered per domain: domains gives each one's own state, and the site is partial, with missingOn naming the domains, when the widget is live on some of them and not on the others. Never call a partial site live everywhere. When nothing has ever reported in, it returns the exact script tag to paste — or, on a Shopify store, says that the widget is a theme app embed which can only be switched on from the Shopify admin, and on a Wix site, that the app manages the script itself and what is missing is a published site or an unpaused app. No assistant can do those steps. On paid plans it includes what daily monitoring last found on the monitored pages (widget running, script present but not running, or absent); that check is what decides the answer when it is recent. What it does NOT do: it does not fetch the customer's site itself, so on a site without a recent monitoring check it cannot see an embed that has been installed but not yet visited by anyone. It does not switch the widget on or off, and it reports no accessibility findings — site_overview and the finding tools own those. Works on every plan including Free. Read-only: four indexed reads, no page load.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteYesThe website domain as registered in Inclusify, e.g. "example.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint, but the description goes well beyond them: it discloses the cost profile ('four indexed reads, no page load'), the key limitation ('does not fetch the customer's site itself', so unseen embeds are invisible), plan availability ('Works on every plan including Free'), and the exact failure-mode behavior. There is no contradiction with the read-only annotations.

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?

Well front-loaded: the when-to-use trigger precedes the mechanics, and the does-not-do list is clearly marked at the end. It is nonetheless long for a one-parameter read tool, with some restated cautions ('Never report the enabled flag as installation' / 'Never call a `partial` site live everywhere') that could be tightened.

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?

With no output schema, the description carries the full return-shape burden and does: the two separate facts, the per-domain `partial`/`missingOn` behavior, the script-tag fallback, the Shopify/Wix variants, and the monitoring-check status values. An agent has everything needed to interpret the response and set expectations.

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 coverage is 100% for the single `website` parameter, which the schema already documents as a registered domain string. The description's domain-level discussion (`domains`, `missingOn`, `partial`) describes response semantics rather than adding parameter syntax or meaning, so the baseline 3 applies.

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 names a specific question space (widget status) and enumerates the exact user phrasings it answers ('is it installed', 'is it live for visitors'). It explicitly separates the widget-installation question from the accessibility-findings question owned by site_overview and the finding tools, so the agent can route without opening either schema.

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?

Opens with an explicit when-to-use clause and a list of triggering questions, then adds when-not ('reports no accessibility findings – site_overview and the finding tools own those'). It also implicitly routes the mutation case by stating 'It does not switch the widget on or off', pointing to set_widget_enabled.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources