Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp

Add another domain to a website

add_domain
Idempotent

Use this when a site Inclusify already knows about is reachable on ANOTHER hostname the widget also needs to serve on — a country TLD, a subdomain, a staging host. WRITES to this website's Inclusify configuration, never to the site itself: no code, theme or DNS is touched, and adding a hostname here does not make it resolve. For a site Inclusify has never heard of, use add_website instead — this tool only adds to an existing one. The new hostname must be the SAME NAME as the site's existing domains: from "example.com" you may add "example.co.uk" or "shop.example.com", but not "somethingelse.com" — that is refused, and the refusal says what would have been allowed. Localhost and IP addresses are refused. A domain already registered to another Inclusify account is refused and needs support, because a hostname belongs to exactly one account. The first domain on a website becomes its primary; later ones do not. After adding, the widget must still be installed on that hostname — call widget_status to check whether it has reported in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe new hostname to add, e.g. "example.co.uk" or "shop.example.com". A URL works too and is reduced to its host. Must share a name with the website's existing domains.
websiteYesThe website to add TO, as already registered in Inclusify, e.g. "example.com".

TDQS

A5/5.0
Behavior5/5

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

The description discloses significant behavioral details beyond annotations: it 'WRITES to this website's Inclusify configuration, never to the site itself', touches no code/theme/DNS, does not make the hostname resolve, and explains primary domain behavior. These are important side effects and constraints that annotations do not capture.

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?

The description is dense but every sentence serves a purpose: when to use, what it does/doesn't do, constraints, primary-domain rule, and follow-up action. It is well structured and front-loaded with the most important usage guidance.

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 a mutating tool with no output schema and no readonly annnotations, the description covers all necessary context: purpose, side effects, constraints, error refusals, primary-domain semantics, and the follow-up step to check widget installation. An agent has enough information to invoke it correctly and set expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaningful parameter semantics: the new hostname must share a name with existing domains, URLs are reduced to their host, and localhost/IPs are refused. This goes well beyond the basic schema descriptions.

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 states a specific verb and resource: 'add another domain to a website' and clarifies it applies to 'a site Inclusify already knows about' on 'ANOTHER hostname'. It explicitly distinguishes itself from add_website, making the tool's scope and purpose unambiguous.

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 gives explicit when-to-use context: when a known site is reachable on another hostname. It also names the alternative, add_website, for 'a site Inclusify has never heard of', and lists refusal cases such as mismatched names, localhost, IP addresses, and domains registered to another account. This leaves no ambiguity about when to choose this tool.

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