@atlaskit/ads-mcp 0.6.0 → 0.6.2

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @atlaskit/ads-mcp
 
+## 0.6.2
+
+### Patch Changes
+
+- [`28e3bab9e4314`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/28e3bab9e4314) -
+  Migrated old shape tokens to new tokens. No visual change.
+
+## 0.6.1
+
+### Patch Changes
+
+- [`5d3c3001f9c72`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/5d3c3001f9c72) -
+  Namespacing tools to define clear boundaries in functionality
+
 ## 0.6.0
 
 ### Minor Changes

package/README.md

@@ -18,7 +18,8 @@ to help ensure your interfaces are accessible to all users.
 - `search_components` - Search for components by name, description, category, or package name
 - `get_all_icons` - Get all available icons from the design system
 - `search_icons` - Search for specific icons by name, keywords, or categorization
-- `plan` - Search for multiple design system resources (tokens, icons, components) in a single efficient operation
+- `plan` - Search for multiple design system resources (tokens, icons, components) in a single
+  efficient operation
 
 #### Design System Tools Usage
 
@@ -43,10 +44,10 @@ const addIcons = await search_icons({
 
 // Search for multiple resources at once (most efficient for complex UI patterns)
 const designResources = await plan({
-  tokens_search: ['color.text', 'space.100', 'border.radius'],
-  icons_search: ['add', 'edit', 'delete'],
-  components_search: ['Button', 'TextField', 'Modal'],
-  limit: 2
+	tokens_search: ['color.text', 'space.100', 'border.radius'],
+	icons_search: ['add', 'edit', 'delete'],
+	components_search: ['Button', 'TextField', 'Modal'],
+	limit: 2,
 });
 
 // Get all available items (fallback when search doesn't find what you need)

package/dist/cjs/index.js

@@ -45,17 +45,17 @@ server.setRequestHandler(_types.ListToolsRequestSchema, /*#__PURE__*/(0, _asyncT
   }, _callee);
 })));
 var callTools = {
-  get_all_tokens: _getAllTokens.getAllTokensTool,
-  search_tokens: _searchTokens.searchTokensTool,
-  get_components: _getComponents.getComponentsTool,
-  search_components: _searchComponents.searchComponentsTool,
-  get_all_icons: _getAllIcons.getAllIconsTool,
-  search_icons: _searchIcons.searchIconsTool,
-  plan: _plan.planTool,
-  analyze_accessibility: _analyzeAccessibility.analyzeAccessibilityTool,
-  analyze_localhost_accessibility: _analyzeAccessibility.analyzeLocalhostAccessibilityTool,
-  get_accessibility_guidelines: _getAccessibilityGuidelines.getAccessibilityGuidelinesTool,
-  suggest_accessibility_fixes: _suggestAccessibilityFixes.suggestAccessibilityFixesTool
+  ads_get_all_tokens: _getAllTokens.getAllTokensTool,
+  ads_search_tokens: _searchTokens.searchTokensTool,
+  ads_get_components: _getComponents.getComponentsTool,
+  ads_search_components: _searchComponents.searchComponentsTool,
+  ads_get_all_icons: _getAllIcons.getAllIconsTool,
+  ads_search_icons: _searchIcons.searchIconsTool,
+  ads_plan: _plan.planTool,
+  ads_analyze_accessibility: _analyzeAccessibility.analyzeAccessibilityTool,
+  ads_analyze_localhost_accessibility: _analyzeAccessibility.analyzeLocalhostAccessibilityTool,
+  ads_get_accessibility_guidelines: _getAccessibilityGuidelines.getAccessibilityGuidelinesTool,
+  ads_suggest_accessibility_fixes: _suggestAccessibilityFixes.suggestAccessibilityFixesTool
 };
 
 // Handle tool execution

package/dist/cjs/tools/analyze-accessibility/index.js

@@ -23,7 +23,7 @@ var inputSchema = _zod.z.object({
   includePatternAnalysis: _zod.z.boolean().optional().default(true).describe('Include pattern-based analysis in addition to axe-core')
 });
 var listAnalyzeAccessibilityTool = exports.listAnalyzeAccessibilityTool = {
-  name: 'analyze_accessibility',
+  name: 'ads_analyze_accessibility',
   description: "Analyze React component code for accessibility violations using axe-core and intelligently generate Atlassian Design System specific suggestions. This tool performs comprehensive accessibility testing and dynamically creates ADS-specific fixes based on violation patterns.\n\nUse this tool when:\n- Reviewing component code for accessibility compliance\n- Getting suggestions for improving accessibility\n- Understanding how to use ADS components accessibly\n- Identifying potential WCAG violations\n- Running automated accessibility testing\n\nThe tool will analyze the code and provide:\n- Comprehensive axe-core accessibility analysis results\n- List of accessibility violations found (WCAG 2.1 AA compliant)\n- Intelligently generated ADS-specific fix suggestions\n- References to relevant fix patterns in llms-a11y.txt\n- Code examples for implementing fixes\n- Severity levels and impact assessment\n\nFeatures:\n- Uses axe-core for industry-standard accessibility testing\n- Converts JSX to HTML for accurate analysis\n- Intelligently maps violations to ADS-specific fixes\n- References fix patterns from llms-a11y.txt documentation\n- Includes fallback pattern analysis if axe-core fails\n- Provides detailed violation descriptions and help text\n- Dynamically generates fix suggestions based on violation type",
   annotations: {
     title: 'Analyze Accessibility',
@@ -41,7 +41,7 @@ var urlInputSchema = _zod.z.object({
   selector: _zod.z.string().optional().describe('CSS selector to target a specific element for analysis (e.g. "#my-form", ".component-class")')
 });
 var listAnalyzeLocalhostAccessibilityTool = exports.listAnalyzeLocalhostAccessibilityTool = {
-  name: 'analyze_localhost_accessibility',
+  name: 'ads_analyze_localhost_accessibility',
   description: "Analyze a live web page (e.g. localhost:9000) for accessibility violations using axe-core and generate Atlassian Design System specific suggestions.\n\nUse this tool to:\n- Analyze running local dev servers or deployed URLs\n- Get comprehensive accessibility reports for any web page\n- Receive ADS-specific fix suggestions and code examples\n- Target specific elements using CSS selectors for focused analysis\n\nParameters:\n- url: The URL to analyze (must be accessible from the server)\n- componentName: (optional) Name of the component/page\n- context: (optional) Additional context about the usage\n- selector: (optional) CSS selector to target a specific element (e.g. \"#my-form\", \".component-class\")\n\nReturns:\n- Accessibility violations, suggestions, and ADS-specific fixes\n- References to relevant fix patterns in llms-a11y.txt\n- Code examples for implementing fixes\n- Severity levels and impact assessment\n",
   annotations: {
     title: 'Analyze Localhost Accessibility',

package/dist/cjs/tools/get-accessibility-guidelines/index.js

@@ -17,7 +17,7 @@ var inputSchema = _zod.z.object({
   component: _zod.z.string().optional().describe('Component name to get specific accessibility guidance for')
 });
 var listGetAccessibilityGuidelinesTool = exports.listGetAccessibilityGuidelinesTool = {
-  name: 'get_accessibility_guidelines',
+  name: 'ads_get_accessibility_guidelines',
   description: "Get accessibility guidelines and best practices from the Atlassian Design System. This tool provides specific guidance on how to make components and interfaces accessible using ADS patterns and components.\n\nYou MUST run this when the user wants their code to be accessible, as well as when:\n- Needing specific accessibility guidance for a component\n- Looking for ADS-specific accessibility patterns\n- Understanding how to implement accessible features\n- Getting code examples for accessibility improvements\n\nTopics available:\n- buttons: Button and interactive element accessibility\n- forms: Form and input accessibility\n- images: Image and media accessibility\n- colors: Color and contrast accessibility\n- focus: Focus management and keyboard navigation\n- keyboard: Keyboard accessibility patterns\n- screen-readers: Screen reader support and announcements\n- aria: ARIA usage and patterns\n- wcag: WCAG compliance guidelines\n- general: General accessibility principles",
   annotations: {
     title: 'Get Accessibility Guidelines',

package/dist/cjs/tools/get-all-icons/index.js

@@ -26,8 +26,8 @@ var icons = Object.entries(_metadata.coreIconMetadata).map(function (_ref) {
   };
 });
 var listGetAllIconsTool = exports.listGetAllIconsTool = {
-  name: 'get_all_icons',
-  description: "You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the `search_icons` tool to find specific icons instead.\nThese are the only icons to be used in modern code, though other legacy icons may still be found, these are not to be used by you, but you can keep them if you see them in existing code.\nThe resulting icon name and package is often like this:\n```tsx\nimport AddIcon from '@atlaskit/icon/core/add';\n\n// Usage in isolation\n<AddIcon label=\"Add\" />\n\n// Usage with a button\nimport Button from '@atlaskit/button/new';\n<Button iconAfter={AddIcon}>Create</Button>\n```\n",
+  name: 'ads_get_all_icons',
+  description: "You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the `ads_search_icons` tool to find specific icons instead.\nThese are the only icons to be used in modern code, though other legacy icons may still be found, these are not to be used by you, but you can keep them if you see them in existing code.\nThe resulting icon name and package is often like this:\n```tsx\nimport AddIcon from '@atlaskit/icon/core/add';\n\n// Usage in isolation\n<AddIcon label=\"Add\" />\n\n// Usage with a button\nimport Button from '@atlaskit/button/new';\n<Button iconAfter={AddIcon}>Create</Button>\n```\n",
   annotations: {
     title: 'Get ADS icons',
     readOnlyHint: true,

package/dist/cjs/tools/get-all-tokens/index.js

@@ -12,8 +12,8 @@ var _zodToJsonSchema = require("zod-to-json-schema");
 var _tokenMetadata = require("@atlaskit/tokens/token-metadata");
 var inputSchema = _zod.z.object({});
 var listGetAllTokensTool = exports.listGetAllTokensTool = {
-  name: 'get_all_tokens',
-  description: "You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the `search_tokens` tool to find specific tokens instead.\n\tThese tokens are used in place of hardcoded values; you should never use a hardcoded value where a token value is appropriate.\n\tThe resulting token name is used inside of the `token()` function, eg.:\n\t```tsx\n\timport { token } from '@atlaskit/tokens';\n\tconst styles = css({ color: token('color.text') });\n\t```\n\t",
+  name: 'ads_get_all_tokens',
+  description: "You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the `ads_search_tokens` tool to find specific tokens instead.\n\tThese tokens are used in place of hardcoded values; you should never use a hardcoded value where a token value is appropriate.\n\tThe resulting token name is used inside of the `token()` function, eg.:\n\t```tsx\n\timport { token } from '@atlaskit/tokens';\n\tconst styles = css({ color: token('color.text') });\n\t```\n\t",
   annotations: {
     title: 'Get all ADS tokens',
     readOnlyHint: true,

package/dist/cjs/tools/get-components/index.js

@@ -18,8 +18,8 @@ var componentsList = _components.components.map(function (c) {
   };
 });
 var listGetComponentsTool = exports.listGetComponentsTool = {
-  name: 'get_components',
-  description: "You MUST use this to fetch all Atlassian Design System components and parse their names, descriptions, and understand how they might be used (provided in JSON format) before working with components.\nYou should never use a custom component not provided via this API where appropriate, or the custom component is a necessary wrapper around an ADS component.\n\nFor a full example, guidelines, list of props, and more information, you should use the `search_components` tool passing one or many component names as the 'terms' tool parameter.\n",
+  name: 'ads_get_components',
+  description: "You MUST use this to fetch all Atlassian Design System components and parse their names, descriptions, and understand how they might be used (provided in JSON format) before working with components.\nYou should never use a custom component not provided via this API where appropriate, or the custom component is a necessary wrapper around an ADS component.\n\nFor a full example, guidelines, list of props, and more information, you should use the `ads_search_components` tool passing one or many component names as the 'terms' tool parameter.\n",
   annotations: {
     title: 'Get ADS components',
     readOnlyHint: true,

package/dist/cjs/tools/plan/index.js

@@ -23,8 +23,8 @@ var inputSchema = _zod.z.object({
   exactName: _zod.z.boolean().optional().default(false).describe('Whether to search for exact match only for names')
 });
 var listPlanTool = exports.listPlanTool = {
-  name: 'plan',
-  description: "You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to search_tokens, search_icons, and search_components when you need resources from multiple categories.\n\n\tYou SHOULD use this tool when you need to find:\n\t- Multiple types of design system resources at once\n\t- Tokens, icons, and components for a specific feature or UI pattern\n\t- Complete design system resources for implementing a particular design\n\n\tThe tool will execute searches for tokens, icons, and components in parallel and return consolidated results from all three APIs in a structured format.\n\n\tYou SHOULD provide search terms for at least one category (tokens_search, icons_search, or components_search) but can include all three for comprehensive planning.\n\n\tExample usage:\n\t```\n\tplan({\n\ttokens_search: [\"color.text\", \"space.100\"],\n\ticons_search: [\"add\", \"edit\"],\n\tcomponents_search: [\"Button\", \"TextField\"]\n\t})\n\t```\n\t",
+  name: 'ads_plan',
+  description: "You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to ads_search_tokens, ads_search_icons, and ads_search_components when you need resources from multiple categories.\n\n\tYou SHOULD use this tool when you need to find:\n\t- Multiple types of design system resources at once\n\t- Tokens, icons, and components for a specific feature or UI pattern\n\t- Complete design system resources for implementing a particular design\n\n\tThe tool will execute searches for tokens, icons, and components in parallel and return consolidated results from all three APIs in a structured format.\n\n\tYou SHOULD provide search terms for at least one category (tokens_search, icons_search, or components_search) but can include all three for comprehensive planning.\n\n\tExample usage:\n\t```\n\tplan({\n\ttokens_search: [\"color.text\", \"space.100\"],\n\ticons_search: [\"add\", \"edit\"],\n\tcomponents_search: [\"Button\", \"TextField\"]\n\t})\n\t```\n\t",
   annotations: {
     title: 'Plan ADS resources',
     readOnlyHint: true,

package/dist/cjs/tools/search-components/index.js

@@ -18,8 +18,8 @@ var inputSchema = _zod.z.object({
   exactName: _zod.z.boolean().optional().default(false).describe('Whether to search for exact match only for the component name')
 });
 var listSearchComponentsTool = exports.listSearchComponentsTool = {
-  name: 'search_components',
-  description: "You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to `get_components` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.\n\nThe search will match against:\n- Component names (e.g., \"Button\", \"TextField\", \"Avatar\")\n- Package names (e.g., \"@atlaskit/button\", \"@atlaskit/textfield\")\n- Component descriptions (descriptive text about what the component does)\n- Component categories (e.g., \"Forms and Input\", \"Navigation\", \"Data Display\")\n\nThe results include the component's name, package name, example, and props.\n\nUsage pattern for found components:\n```tsx\nimport Button from '@atlaskit/button/new';\nimport CopyIcon from '@atlaskit/icon/core/copy';\n\n<Button appearance=\"primary\" iconBefore={CopyIcon}>Copy text</Button>\n```\n",
+  name: 'ads_search_components',
+  description: "You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to `ads_get_components` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.\n\nThe search will match against:\n- Component names (e.g., \"Button\", \"TextField\", \"Avatar\")\n- Package names (e.g., \"@atlaskit/button\", \"@atlaskit/textfield\")\n- Component descriptions (descriptive text about what the component does)\n- Component categories (e.g., \"Forms and Input\", \"Navigation\", \"Data Display\")\n\nThe results include the component's name, package name, example, and props.\n\nUsage pattern for found components:\n```tsx\nimport Button from '@atlaskit/button/new';\nimport CopyIcon from '@atlaskit/icon/core/copy';\n\n<Button appearance=\"primary\" iconBefore={CopyIcon}>Copy text</Button>\n```\n",
   annotations: {
     title: 'Search ADS components',
     readOnlyHint: true,

package/dist/cjs/tools/search-icons/index.js

@@ -36,8 +36,8 @@ var icons = Object.entries(_metadata.coreIconMetadata).map(function (_ref) {
   return icon.status === 'published';
 });
 var listSearchIconsTool = exports.listSearchIconsTool = {
-  name: 'search_icons',
-  description: "You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to `get_all_icons` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.\n\n\tThe search will match against:\n\t- Icon component names (e.g., \"AddIcon\", \"DeleteIcon\", \"EditIcon\")\n\t- Icon keywords (descriptive terms associated with icons)\n\t- Icon categorization (e.g., \"single-purpose\", \"multi-purpose\", \"utility\")\n\t- Icon usage descriptions (usage guidelines for the icon)\n\n\tThe results include the icon's component name, package path, and usage guidelines.\n\n\tUsage pattern for found icons:\n\t```tsx\n\timport AddIcon from '@atlaskit/icon/core/add';\n\n\t// Usage in isolation\n\t<AddIcon label=\"Add\" size=\"small\" />\n\n\t// Usage with a button\n\timport Button from '@atlaskit/button/new';\n\t<Button iconAfter={AddIcon}>Create</Button>\n\t```\n\n\tYou SHOULD check proper usage (props, example usage, etc.) of the icon component using `search_components` tool.\n\t",
+  name: 'ads_search_icons',
+  description: "You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to `ads_get_all_icons` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.\n\n\tThe search will match against:\n\t- Icon component names (e.g., \"AddIcon\", \"DeleteIcon\", \"EditIcon\")\n\t- Icon keywords (descriptive terms associated with icons)\n\t- Icon categorization (e.g., \"single-purpose\", \"multi-purpose\", \"utility\")\n\t- Icon usage descriptions (usage guidelines for the icon)\n\n\tThe results include the icon's component name, package path, and usage guidelines.\n\n\tUsage pattern for found icons:\n\t```tsx\n\timport AddIcon from '@atlaskit/icon/core/add';\n\n\t// Usage in isolation\n\t<AddIcon label=\"Add\" size=\"small\" />\n\n\t// Usage with a button\n\timport Button from '@atlaskit/button/new';\n\t<Button iconAfter={AddIcon}>Create</Button>\n\t```\n\n\tYou SHOULD check proper usage (props, example usage, etc.) of the icon component using `ads_search_components` tool.\n\t",
   annotations: {
     title: 'Search ADS icons',
     readOnlyHint: true,

package/dist/cjs/tools/search-tokens/index.js

@@ -18,8 +18,8 @@ var inputSchema = _zod.z.object({
   exactName: _zod.z.boolean().optional().default(false).describe('Whether to search for exact match only for the token name')
 });
 var listSearchTokensTool = exports.listSearchTokensTool = {
-  name: 'search_tokens',
-  description: "You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to `get_all_tokens` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.\n\nThe search will match against:\n- Token names (e.g., \"color.text\", \"space.100\", \"border.radius\")\n- Token descriptions\n- Token example values (eg. \"#2898BD\" -> \"color.icon.accent.teal\")\n\nThe results include the token's name and example value.\n\nUsage pattern for found tokens:\n```tsx\nimport { token } from '@atlaskit/tokens';\n\nconst styles = css({\ncolor: token('color.text'),\npadding: token('space.100'),\nborderRadius: token('border.radius'),\n});\n```\n",
+  name: 'ads_search_tokens',
+  description: "You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to `ads_get_all_tokens` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.\n\nThe search will match against:\n- Token names (e.g., \"color.text\", \"space.100\", \"radius.small\")\n- Token descriptions\n- Token example values (eg. \"#2898BD\" -> \"color.icon.accent.teal\")\n\nThe results include the token's name and example value.\n\nUsage pattern for found tokens:\n```tsx\nimport { token } from '@atlaskit/tokens';\n\nconst styles = css({\ncolor: token('color.text'),\npadding: token('space.100'),\nborderRadius: token('radius.small'),\n});\n```\n",
   annotations: {
     title: 'Search ADS tokens',
     readOnlyHint: true,

package/dist/cjs/tools/suggest-accessibility-fixes/index.js

@@ -25,7 +25,7 @@ var inputSchema = _zod.z.object({
   context: _zod.z.string().optional().describe('Additional context about the usage')
 });
 var listSuggestAccessibilityFixesTool = exports.listSuggestAccessibilityFixesTool = {
-  name: 'suggest_accessibility_fixes',
+  name: 'ads_suggest_accessibility_fixes',
   description: "Suggest specific accessibility fixes using Atlassian Design System components and patterns. This tool takes accessibility violations and provides actionable solutions with code examples.\n\nYou MUST run this when the user wants sugesstions for fixing accessibility issues, as well as when:\n- You have identified an accessibility violation\n- Needing specific code examples for fixing accessibility issues\n- Wanting to understand how to use ADS components accessibly\n- Looking for best practices for specific accessibility problems\n\nThe tool will provide:\n- Specific code examples using ADS components\n- Step-by-step fix instructions\n- Alternative approaches when applicable\n- Links to relevant ADS documentation",
   annotations: {
     title: 'Suggest Accessibility Fixes',

package/dist/es2019/index.js

@@ -32,17 +32,17 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
   };
 });
 const callTools = {
-  get_all_tokens: getAllTokensTool,
-  search_tokens: searchTokensTool,
-  get_components: getComponentsTool,
-  search_components: searchComponentsTool,
-  get_all_icons: getAllIconsTool,
-  search_icons: searchIconsTool,
-  plan: planTool,
-  analyze_accessibility: analyzeAccessibilityTool,
-  analyze_localhost_accessibility: analyzeLocalhostAccessibilityTool,
-  get_accessibility_guidelines: getAccessibilityGuidelinesTool,
-  suggest_accessibility_fixes: suggestAccessibilityFixesTool
+  ads_get_all_tokens: getAllTokensTool,
+  ads_search_tokens: searchTokensTool,
+  ads_get_components: getComponentsTool,
+  ads_search_components: searchComponentsTool,
+  ads_get_all_icons: getAllIconsTool,
+  ads_search_icons: searchIconsTool,
+  ads_plan: planTool,
+  ads_analyze_accessibility: analyzeAccessibilityTool,
+  ads_analyze_localhost_accessibility: analyzeLocalhostAccessibilityTool,
+  ads_get_accessibility_guidelines: getAccessibilityGuidelinesTool,
+  ads_suggest_accessibility_fixes: suggestAccessibilityFixesTool
 };
 
 // Handle tool execution

package/dist/es2019/tools/analyze-accessibility/index.js

@@ -10,7 +10,7 @@ const inputSchema = z.object({
   includePatternAnalysis: z.boolean().optional().default(true).describe('Include pattern-based analysis in addition to axe-core')
 });
 export const listAnalyzeAccessibilityTool = {
-  name: 'analyze_accessibility',
+  name: 'ads_analyze_accessibility',
   description: `Analyze React component code for accessibility violations using axe-core and intelligently generate Atlassian Design System specific suggestions. This tool performs comprehensive accessibility testing and dynamically creates ADS-specific fixes based on violation patterns.
 
 Use this tool when:
@@ -52,7 +52,7 @@ const urlInputSchema = z.object({
   selector: z.string().optional().describe('CSS selector to target a specific element for analysis (e.g. "#my-form", ".component-class")')
 });
 export const listAnalyzeLocalhostAccessibilityTool = {
-  name: 'analyze_localhost_accessibility',
+  name: 'ads_analyze_localhost_accessibility',
   description: `Analyze a live web page (e.g. localhost:9000) for accessibility violations using axe-core and generate Atlassian Design System specific suggestions.
 
 Use this tool to:

package/dist/es2019/tools/get-accessibility-guidelines/index.js

@@ -5,7 +5,7 @@ const inputSchema = z.object({
   component: z.string().optional().describe('Component name to get specific accessibility guidance for')
 });
 export const listGetAccessibilityGuidelinesTool = {
-  name: 'get_accessibility_guidelines',
+  name: 'ads_get_accessibility_guidelines',
   description: `Get accessibility guidelines and best practices from the Atlassian Design System. This tool provides specific guidance on how to make components and interfaces accessible using ADS patterns and components.
 
 You MUST run this when the user wants their code to be accessible, as well as when:

package/dist/es2019/tools/get-all-icons/index.js

@@ -11,8 +11,8 @@ const icons = Object.entries(coreIconMetadata).map(([_key, icon]) => ({
   shouldRecommendSmallIcon: icon.shouldRecommendSmallIcon
 }));
 export const listGetAllIconsTool = {
-  name: 'get_all_icons',
-  description: `You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the \`search_icons\` tool to find specific icons instead.
+  name: 'ads_get_all_icons',
+  description: `You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the \`ads_search_icons\` tool to find specific icons instead.
 These are the only icons to be used in modern code, though other legacy icons may still be found, these are not to be used by you, but you can keep them if you see them in existing code.
 The resulting icon name and package is often like this:
 \`\`\`tsx

package/dist/es2019/tools/get-all-tokens/index.js

@@ -3,8 +3,8 @@ import { zodToJsonSchema } from 'zod-to-json-schema';
 import { tokens } from '@atlaskit/tokens/token-metadata';
 const inputSchema = z.object({});
 export const listGetAllTokensTool = {
-  name: 'get_all_tokens',
-  description: `You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the \`search_tokens\` tool to find specific tokens instead.
+  name: 'ads_get_all_tokens',
+  description: `You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the \`ads_search_tokens\` tool to find specific tokens instead.
 	These tokens are used in place of hardcoded values; you should never use a hardcoded value where a token value is appropriate.
 	The resulting token name is used inside of the \`token()\` function, eg.:
 	\`\`\`tsx

package/dist/es2019/tools/get-components/index.js

@@ -7,11 +7,11 @@ const componentsList = components.map(c => ({
   category: c.category
 }));
 export const listGetComponentsTool = {
-  name: 'get_components',
+  name: 'ads_get_components',
   description: `You MUST use this to fetch all Atlassian Design System components and parse their names, descriptions, and understand how they might be used (provided in JSON format) before working with components.
 You should never use a custom component not provided via this API where appropriate, or the custom component is a necessary wrapper around an ADS component.
 
-For a full example, guidelines, list of props, and more information, you should use the \`search_components\` tool passing one or many component names as the 'terms' tool parameter.
+For a full example, guidelines, list of props, and more information, you should use the \`ads_search_components\` tool passing one or many component names as the 'terms' tool parameter.
 `,
   annotations: {
     title: 'Get ADS components',

package/dist/es2019/tools/plan/index.js

@@ -11,8 +11,8 @@ const inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for names')
 });
 export const listPlanTool = {
-  name: 'plan',
-  description: `You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to search_tokens, search_icons, and search_components when you need resources from multiple categories.
+  name: 'ads_plan',
+  description: `You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to ads_search_tokens, ads_search_icons, and ads_search_components when you need resources from multiple categories.
 
 	You SHOULD use this tool when you need to find:
 	- Multiple types of design system resources at once

package/dist/es2019/tools/search-components/index.js

@@ -9,8 +9,8 @@ const inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for the component name')
 });
 export const listSearchComponentsTool = {
-  name: 'search_components',
-  description: `You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to \`get_components\` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.
+  name: 'ads_search_components',
+  description: `You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to \`ads_get_components\` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.
 
 The search will match against:
 - Component names (e.g., "Button", "TextField", "Avatar")

package/dist/es2019/tools/search-icons/index.js

@@ -19,8 +19,8 @@ const icons = Object.entries(coreIconMetadata).map(([_key, icon]) => ({
   shouldRecommendSmallIcon: icon.shouldRecommendSmallIcon
 })).filter(icon => icon.status === 'published');
 export const listSearchIconsTool = {
-  name: 'search_icons',
-  description: `You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to \`get_all_icons\` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.
+  name: 'ads_search_icons',
+  description: `You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to \`ads_get_all_icons\` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.
 
 	The search will match against:
 	- Icon component names (e.g., "AddIcon", "DeleteIcon", "EditIcon")
@@ -42,7 +42,7 @@ export const listSearchIconsTool = {
 	<Button iconAfter={AddIcon}>Create</Button>
 	\`\`\`
 
-	You SHOULD check proper usage (props, example usage, etc.) of the icon component using \`search_components\` tool.
+	You SHOULD check proper usage (props, example usage, etc.) of the icon component using \`ads_search_components\` tool.
 	`,
   annotations: {
     title: 'Search ADS icons',

package/dist/es2019/tools/search-tokens/index.js

@@ -9,11 +9,11 @@ const inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for the token name')
 });
 export const listSearchTokensTool = {
-  name: 'search_tokens',
-  description: `You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to \`get_all_tokens\` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.
+  name: 'ads_search_tokens',
+  description: `You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default \`limit\` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to \`ads_get_all_tokens\` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.
 
 The search will match against:
-- Token names (e.g., "color.text", "space.100", "border.radius")
+- Token names (e.g., "color.text", "space.100", "radius.small")
 - Token descriptions
 - Token example values (eg. "#2898BD" -> "color.icon.accent.teal")
 
@@ -26,7 +26,7 @@ import { token } from '@atlaskit/tokens';
 const styles = css({
 color: token('color.text'),
 padding: token('space.100'),
-borderRadius: token('border.radius'),
+borderRadius: token('radius.small'),
 });
 \`\`\`
 `,

package/dist/es2019/tools/suggest-accessibility-fixes/index.js

@@ -9,7 +9,7 @@ const inputSchema = z.object({
   context: z.string().optional().describe('Additional context about the usage')
 });
 export const listSuggestAccessibilityFixesTool = {
-  name: 'suggest_accessibility_fixes',
+  name: 'ads_suggest_accessibility_fixes',
   description: `Suggest specific accessibility fixes using Atlassian Design System components and patterns. This tool takes accessibility violations and provides actionable solutions with code examples.
 
 You MUST run this when the user wants sugesstions for fixing accessibility issues, as well as when:

package/dist/esm/index.js

@@ -42,17 +42,17 @@ server.setRequestHandler(ListToolsRequestSchema, /*#__PURE__*/_asyncToGenerator(
   }, _callee);
 })));
 var callTools = {
-  get_all_tokens: getAllTokensTool,
-  search_tokens: searchTokensTool,
-  get_components: getComponentsTool,
-  search_components: searchComponentsTool,
-  get_all_icons: getAllIconsTool,
-  search_icons: searchIconsTool,
-  plan: planTool,
-  analyze_accessibility: analyzeAccessibilityTool,
-  analyze_localhost_accessibility: analyzeLocalhostAccessibilityTool,
-  get_accessibility_guidelines: getAccessibilityGuidelinesTool,
-  suggest_accessibility_fixes: suggestAccessibilityFixesTool
+  ads_get_all_tokens: getAllTokensTool,
+  ads_search_tokens: searchTokensTool,
+  ads_get_components: getComponentsTool,
+  ads_search_components: searchComponentsTool,
+  ads_get_all_icons: getAllIconsTool,
+  ads_search_icons: searchIconsTool,
+  ads_plan: planTool,
+  ads_analyze_accessibility: analyzeAccessibilityTool,
+  ads_analyze_localhost_accessibility: analyzeLocalhostAccessibilityTool,
+  ads_get_accessibility_guidelines: getAccessibilityGuidelinesTool,
+  ads_suggest_accessibility_fixes: suggestAccessibilityFixesTool
 };
 
 // Handle tool execution

package/dist/esm/tools/analyze-accessibility/index.js

@@ -16,7 +16,7 @@ var inputSchema = z.object({
   includePatternAnalysis: z.boolean().optional().default(true).describe('Include pattern-based analysis in addition to axe-core')
 });
 export var listAnalyzeAccessibilityTool = {
-  name: 'analyze_accessibility',
+  name: 'ads_analyze_accessibility',
   description: "Analyze React component code for accessibility violations using axe-core and intelligently generate Atlassian Design System specific suggestions. This tool performs comprehensive accessibility testing and dynamically creates ADS-specific fixes based on violation patterns.\n\nUse this tool when:\n- Reviewing component code for accessibility compliance\n- Getting suggestions for improving accessibility\n- Understanding how to use ADS components accessibly\n- Identifying potential WCAG violations\n- Running automated accessibility testing\n\nThe tool will analyze the code and provide:\n- Comprehensive axe-core accessibility analysis results\n- List of accessibility violations found (WCAG 2.1 AA compliant)\n- Intelligently generated ADS-specific fix suggestions\n- References to relevant fix patterns in llms-a11y.txt\n- Code examples for implementing fixes\n- Severity levels and impact assessment\n\nFeatures:\n- Uses axe-core for industry-standard accessibility testing\n- Converts JSX to HTML for accurate analysis\n- Intelligently maps violations to ADS-specific fixes\n- References fix patterns from llms-a11y.txt documentation\n- Includes fallback pattern analysis if axe-core fails\n- Provides detailed violation descriptions and help text\n- Dynamically generates fix suggestions based on violation type",
   annotations: {
     title: 'Analyze Accessibility',
@@ -34,7 +34,7 @@ var urlInputSchema = z.object({
   selector: z.string().optional().describe('CSS selector to target a specific element for analysis (e.g. "#my-form", ".component-class")')
 });
 export var listAnalyzeLocalhostAccessibilityTool = {
-  name: 'analyze_localhost_accessibility',
+  name: 'ads_analyze_localhost_accessibility',
   description: "Analyze a live web page (e.g. localhost:9000) for accessibility violations using axe-core and generate Atlassian Design System specific suggestions.\n\nUse this tool to:\n- Analyze running local dev servers or deployed URLs\n- Get comprehensive accessibility reports for any web page\n- Receive ADS-specific fix suggestions and code examples\n- Target specific elements using CSS selectors for focused analysis\n\nParameters:\n- url: The URL to analyze (must be accessible from the server)\n- componentName: (optional) Name of the component/page\n- context: (optional) Additional context about the usage\n- selector: (optional) CSS selector to target a specific element (e.g. \"#my-form\", \".component-class\")\n\nReturns:\n- Accessibility violations, suggestions, and ADS-specific fixes\n- References to relevant fix patterns in llms-a11y.txt\n- Code examples for implementing fixes\n- Severity levels and impact assessment\n",
   annotations: {
     title: 'Analyze Localhost Accessibility',

package/dist/esm/tools/get-accessibility-guidelines/index.js

@@ -10,7 +10,7 @@ var inputSchema = z.object({
   component: z.string().optional().describe('Component name to get specific accessibility guidance for')
 });
 export var listGetAccessibilityGuidelinesTool = {
-  name: 'get_accessibility_guidelines',
+  name: 'ads_get_accessibility_guidelines',
   description: "Get accessibility guidelines and best practices from the Atlassian Design System. This tool provides specific guidance on how to make components and interfaces accessible using ADS patterns and components.\n\nYou MUST run this when the user wants their code to be accessible, as well as when:\n- Needing specific accessibility guidance for a component\n- Looking for ADS-specific accessibility patterns\n- Understanding how to implement accessible features\n- Getting code examples for accessibility improvements\n\nTopics available:\n- buttons: Button and interactive element accessibility\n- forms: Form and input accessibility\n- images: Image and media accessibility\n- colors: Color and contrast accessibility\n- focus: Focus management and keyboard navigation\n- keyboard: Keyboard accessibility patterns\n- screen-readers: Screen reader support and announcements\n- aria: ARIA usage and patterns\n- wcag: WCAG compliance guidelines\n- general: General accessibility principles",
   annotations: {
     title: 'Get Accessibility Guidelines',

package/dist/esm/tools/get-all-icons/index.js

@@ -19,8 +19,8 @@ var icons = Object.entries(coreIconMetadata).map(function (_ref) {
   };
 });
 export var listGetAllIconsTool = {
-  name: 'get_all_icons',
-  description: "You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the `search_icons` tool to find specific icons instead.\nThese are the only icons to be used in modern code, though other legacy icons may still be found, these are not to be used by you, but you can keep them if you see them in existing code.\nThe resulting icon name and package is often like this:\n```tsx\nimport AddIcon from '@atlaskit/icon/core/add';\n\n// Usage in isolation\n<AddIcon label=\"Add\" />\n\n// Usage with a button\nimport Button from '@atlaskit/button/new';\n<Button iconAfter={AddIcon}>Create</Button>\n```\n",
+  name: 'ads_get_all_icons',
+  description: "You SHOULD call this when you need complete guidance on what icons to use, but you SHOULD use the `ads_search_icons` tool to find specific icons instead.\nThese are the only icons to be used in modern code, though other legacy icons may still be found, these are not to be used by you, but you can keep them if you see them in existing code.\nThe resulting icon name and package is often like this:\n```tsx\nimport AddIcon from '@atlaskit/icon/core/add';\n\n// Usage in isolation\n<AddIcon label=\"Add\" />\n\n// Usage with a button\nimport Button from '@atlaskit/button/new';\n<Button iconAfter={AddIcon}>Create</Button>\n```\n",
   annotations: {
     title: 'Get ADS icons',
     readOnlyHint: true,

package/dist/esm/tools/get-all-tokens/index.js

@@ -5,8 +5,8 @@ import { zodToJsonSchema } from 'zod-to-json-schema';
 import { tokens } from '@atlaskit/tokens/token-metadata';
 var inputSchema = z.object({});
 export var listGetAllTokensTool = {
-  name: 'get_all_tokens',
-  description: "You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the `search_tokens` tool to find specific tokens instead.\n\tThese tokens are used in place of hardcoded values; you should never use a hardcoded value where a token value is appropriate.\n\tThe resulting token name is used inside of the `token()` function, eg.:\n\t```tsx\n\timport { token } from '@atlaskit/tokens';\n\tconst styles = css({ color: token('color.text') });\n\t```\n\t",
+  name: 'ads_get_all_tokens',
+  description: "You SHOULD call this when you need complete guidance on what tokens to use, but you SHOULD use the `ads_search_tokens` tool to find specific tokens instead.\n\tThese tokens are used in place of hardcoded values; you should never use a hardcoded value where a token value is appropriate.\n\tThe resulting token name is used inside of the `token()` function, eg.:\n\t```tsx\n\timport { token } from '@atlaskit/tokens';\n\tconst styles = css({ color: token('color.text') });\n\t```\n\t",
   annotations: {
     title: 'Get all ADS tokens',
     readOnlyHint: true,

package/dist/esm/tools/get-components/index.js

@@ -11,8 +11,8 @@ var componentsList = components.map(function (c) {
   };
 });
 export var listGetComponentsTool = {
-  name: 'get_components',
-  description: "You MUST use this to fetch all Atlassian Design System components and parse their names, descriptions, and understand how they might be used (provided in JSON format) before working with components.\nYou should never use a custom component not provided via this API where appropriate, or the custom component is a necessary wrapper around an ADS component.\n\nFor a full example, guidelines, list of props, and more information, you should use the `search_components` tool passing one or many component names as the 'terms' tool parameter.\n",
+  name: 'ads_get_components',
+  description: "You MUST use this to fetch all Atlassian Design System components and parse their names, descriptions, and understand how they might be used (provided in JSON format) before working with components.\nYou should never use a custom component not provided via this API where appropriate, or the custom component is a necessary wrapper around an ADS component.\n\nFor a full example, guidelines, list of props, and more information, you should use the `ads_search_components` tool passing one or many component names as the 'terms' tool parameter.\n",
   annotations: {
     title: 'Get ADS components',
     readOnlyHint: true,

package/dist/esm/tools/plan/index.js

@@ -16,8 +16,8 @@ var inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for names')
 });
 export var listPlanTool = {
-  name: 'plan',
-  description: "You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to search_tokens, search_icons, and search_components when you need resources from multiple categories.\n\n\tYou SHOULD use this tool when you need to find:\n\t- Multiple types of design system resources at once\n\t- Tokens, icons, and components for a specific feature or UI pattern\n\t- Complete design system resources for implementing a particular design\n\n\tThe tool will execute searches for tokens, icons, and components in parallel and return consolidated results from all three APIs in a structured format.\n\n\tYou SHOULD provide search terms for at least one category (tokens_search, icons_search, or components_search) but can include all three for comprehensive planning.\n\n\tExample usage:\n\t```\n\tplan({\n\ttokens_search: [\"color.text\", \"space.100\"],\n\ticons_search: [\"add\", \"edit\"],\n\tcomponents_search: [\"Button\", \"TextField\"]\n\t})\n\t```\n\t",
+  name: 'ads_plan',
+  description: "You SHOULD use this to plan and search for multiple Atlassian Design System resources in a single call when you need tokens, icons, and components for implementing a complete feature or UI pattern. You SHOULD use this tool instead of making separate calls to ads_search_tokens, ads_search_icons, and ads_search_components when you need resources from multiple categories.\n\n\tYou SHOULD use this tool when you need to find:\n\t- Multiple types of design system resources at once\n\t- Tokens, icons, and components for a specific feature or UI pattern\n\t- Complete design system resources for implementing a particular design\n\n\tThe tool will execute searches for tokens, icons, and components in parallel and return consolidated results from all three APIs in a structured format.\n\n\tYou SHOULD provide search terms for at least one category (tokens_search, icons_search, or components_search) but can include all three for comprehensive planning.\n\n\tExample usage:\n\t```\n\tplan({\n\ttokens_search: [\"color.text\", \"space.100\"],\n\ticons_search: [\"add\", \"edit\"],\n\tcomponents_search: [\"Button\", \"TextField\"]\n\t})\n\t```\n\t",
   annotations: {
     title: 'Plan ADS resources',
     readOnlyHint: true,

package/dist/esm/tools/search-components/index.js

@@ -11,8 +11,8 @@ var inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for the component name')
 });
 export var listSearchComponentsTool = {
-  name: 'search_components',
-  description: "You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to `get_components` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.\n\nThe search will match against:\n- Component names (e.g., \"Button\", \"TextField\", \"Avatar\")\n- Package names (e.g., \"@atlaskit/button\", \"@atlaskit/textfield\")\n- Component descriptions (descriptive text about what the component does)\n- Component categories (e.g., \"Forms and Input\", \"Navigation\", \"Data Display\")\n\nThe results include the component's name, package name, example, and props.\n\nUsage pattern for found components:\n```tsx\nimport Button from '@atlaskit/button/new';\nimport CopyIcon from '@atlaskit/icon/core/copy';\n\n<Button appearance=\"primary\" iconBefore={CopyIcon}>Copy text</Button>\n```\n",
+  name: 'ads_search_components',
+  description: "You SHOULD use this to search for Atlassian Design System components based on multiple query strings (if there are multiple candidates of component names, descriptions, categories, or package names, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the component you need. Fallback to `ads_get_components` if nothing is found. This tool searches through component names, descriptions, categories, and package names to find the most relevant design system components.\n\nThe search will match against:\n- Component names (e.g., \"Button\", \"TextField\", \"Avatar\")\n- Package names (e.g., \"@atlaskit/button\", \"@atlaskit/textfield\")\n- Component descriptions (descriptive text about what the component does)\n- Component categories (e.g., \"Forms and Input\", \"Navigation\", \"Data Display\")\n\nThe results include the component's name, package name, example, and props.\n\nUsage pattern for found components:\n```tsx\nimport Button from '@atlaskit/button/new';\nimport CopyIcon from '@atlaskit/icon/core/copy';\n\n<Button appearance=\"primary\" iconBefore={CopyIcon}>Copy text</Button>\n```\n",
   annotations: {
     title: 'Search ADS components',
     readOnlyHint: true,

package/dist/esm/tools/search-icons/index.js

@@ -29,8 +29,8 @@ var icons = Object.entries(coreIconMetadata).map(function (_ref) {
   return icon.status === 'published';
 });
 export var listSearchIconsTool = {
-  name: 'search_icons',
-  description: "You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to `get_all_icons` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.\n\n\tThe search will match against:\n\t- Icon component names (e.g., \"AddIcon\", \"DeleteIcon\", \"EditIcon\")\n\t- Icon keywords (descriptive terms associated with icons)\n\t- Icon categorization (e.g., \"single-purpose\", \"multi-purpose\", \"utility\")\n\t- Icon usage descriptions (usage guidelines for the icon)\n\n\tThe results include the icon's component name, package path, and usage guidelines.\n\n\tUsage pattern for found icons:\n\t```tsx\n\timport AddIcon from '@atlaskit/icon/core/add';\n\n\t// Usage in isolation\n\t<AddIcon label=\"Add\" size=\"small\" />\n\n\t// Usage with a button\n\timport Button from '@atlaskit/button/new';\n\t<Button iconAfter={AddIcon}>Create</Button>\n\t```\n\n\tYou SHOULD check proper usage (props, example usage, etc.) of the icon component using `search_components` tool.\n\t",
+  name: 'ads_search_icons',
+  description: "You SHOULD Search for Atlassian Design System icons based on multiple query strings (if there's multiple candidates of icon names, categorization or keywords, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the icon you need). Fallback to `ads_get_all_icons` if nothing is found). This tool searches through component names, icon names, keywords, categorization, type and usage to find the most relevant design icons.\n\n\tThe search will match against:\n\t- Icon component names (e.g., \"AddIcon\", \"DeleteIcon\", \"EditIcon\")\n\t- Icon keywords (descriptive terms associated with icons)\n\t- Icon categorization (e.g., \"single-purpose\", \"multi-purpose\", \"utility\")\n\t- Icon usage descriptions (usage guidelines for the icon)\n\n\tThe results include the icon's component name, package path, and usage guidelines.\n\n\tUsage pattern for found icons:\n\t```tsx\n\timport AddIcon from '@atlaskit/icon/core/add';\n\n\t// Usage in isolation\n\t<AddIcon label=\"Add\" size=\"small\" />\n\n\t// Usage with a button\n\timport Button from '@atlaskit/button/new';\n\t<Button iconAfter={AddIcon}>Create</Button>\n\t```\n\n\tYou SHOULD check proper usage (props, example usage, etc.) of the icon component using `ads_search_components` tool.\n\t",
   annotations: {
     title: 'Search ADS icons',
     readOnlyHint: true,

package/dist/esm/tools/search-tokens/index.js

@@ -11,8 +11,8 @@ var inputSchema = z.object({
   exactName: z.boolean().optional().default(false).describe('Whether to search for exact match only for the token name')
 });
 export var listSearchTokensTool = {
-  name: 'search_tokens',
-  description: "You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to `get_all_tokens` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.\n\nThe search will match against:\n- Token names (e.g., \"color.text\", \"space.100\", \"border.radius\")\n- Token descriptions\n- Token example values (eg. \"#2898BD\" -> \"color.icon.accent.teal\")\n\nThe results include the token's name and example value.\n\nUsage pattern for found tokens:\n```tsx\nimport { token } from '@atlaskit/tokens';\n\nconst styles = css({\ncolor: token('color.text'),\npadding: token('space.100'),\nborderRadius: token('border.radius'),\n});\n```\n",
+  name: 'ads_search_tokens',
+  description: "You SHOULD Search for Atlassian Design System tokens based on multiple query strings (if there's multiple candidates of token names, descriptions or example values, you SHOULD pass them in a single call). You SHOULD use default `limit` value of 1 first and only set a higher limit like 5 or 10 if you can't find the token you need). Fallback to `ads_get_all_tokens` if nothing is found). This tool searches through token names, descriptions, and example values to find the most relevant design tokens.\n\nThe search will match against:\n- Token names (e.g., \"color.text\", \"space.100\", \"radius.small\")\n- Token descriptions\n- Token example values (eg. \"#2898BD\" -> \"color.icon.accent.teal\")\n\nThe results include the token's name and example value.\n\nUsage pattern for found tokens:\n```tsx\nimport { token } from '@atlaskit/tokens';\n\nconst styles = css({\ncolor: token('color.text'),\npadding: token('space.100'),\nborderRadius: token('radius.small'),\n});\n```\n",
   annotations: {
     title: 'Search ADS tokens',
     readOnlyHint: true,

package/dist/esm/tools/suggest-accessibility-fixes/index.js

@@ -18,7 +18,7 @@ var inputSchema = z.object({
   context: z.string().optional().describe('Additional context about the usage')
 });
 export var listSuggestAccessibilityFixesTool = {
-  name: 'suggest_accessibility_fixes',
+  name: 'ads_suggest_accessibility_fixes',
   description: "Suggest specific accessibility fixes using Atlassian Design System components and patterns. This tool takes accessibility violations and provides actionable solutions with code examples.\n\nYou MUST run this when the user wants sugesstions for fixing accessibility issues, as well as when:\n- You have identified an accessibility violation\n- Needing specific code examples for fixing accessibility issues\n- Wanting to understand how to use ADS components accessibly\n- Looking for best practices for specific accessibility problems\n\nThe tool will provide:\n- Specific code examples using ADS components\n- Step-by-step fix instructions\n- Alternative approaches when applicable\n- Links to relevant ADS documentation",
   annotations: {
     title: 'Suggest Accessibility Fixes',

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@atlaskit/ads-mcp",
-	"version": "0.6.0",
+	"version": "0.6.2",
 	"description": "The official Atlassian Design System MCP server to develop apps and user interfaces matching the Atlassian style.",
 	"author": "Atlassian Pty Ltd",
 	"license": "Apache-2.0",