packages/opencode/src/bundled-skills/mcp-tool-discovery/SKILL.md
This skill should be used when the user asks about "available tools", "what tools", "how to find tools", "tool search", "MCP servers", "list tools", "discover tools", "which tools", or needs guidance on discovering and using Snow-Flow MCP tools.
npx skillsauth add groeimetai/snow-flow mcp-tool-discoveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Snow-Flow provides 400+ tools via MCP (Model Context Protocol) servers. Tools are lazy-loaded to save tokens - use tool_search to discover them.
// Find tools for a specific task
tool_search({ query: "incident" }) // ServiceNow incidents
tool_search({ query: "widget" }) // Widget development
tool_search({ query: "update set" }) // Update Set management
tool_search({ query: "cmdb" }) // CMDB operations
| Query | Tools Found |
| --------------- | ----------------------------------- |
| "incident" | Incident CRUD, metrics, SLA |
| "change" | Change requests, CAB, risk |
| "problem" | Problem management, known errors |
| "cmdb" | CI search, relationships, discovery |
| "user lookup" | User/group queries |
| "query table" | Universal table queries |
| Query | Tools Found |
| ------------------ | -------------------------- |
| "widget" | Widget create/update/sync |
| "business rule" | BR creation and management |
| "script include" | Reusable scripts |
| "client script" | Client-side scripts |
| "ui policy" | Form policies |
| "ui action" | Buttons and links |
| "update set" | Update Set lifecycle |
| "snow deploy" | Artifact deployment |
| Query | Tools Found |
| ----------------- | --------------------------- |
| "flow designer" | Flow/subflow creation |
| "workspace" | Workspace builder |
| "catalog" | Service catalog items |
| "knowledge" | Knowledge articles |
| "notification" | Email notifications |
| "scheduled job" | Scheduled scripts |
| "rest" | REST API integration |
| "import" | Import sets, transform maps |
| Query | Tools Found |
| ----------------- | ------------------------------------ |
| "activity" | Activity tracking (always available) |
| "instance info" | Instance URL and config |
| "property" | System properties |
| "logs" | System logs |
| Query | Tools Found |
| ---------------- | ---------------------------------- |
| "jira" | Jira issues, transitions, comments |
| "azure devops" | Work items, boards, pipelines |
| "confluence" | Pages, spaces, search |
| "github" | Issues, PRs, workflows, releases |
| "gitlab" | Issues, MRs, pipelines |
These tools are loaded by default (no discovery needed):
// Activity tracking
activity_start({ source, storyTitle, storyType, ... })
activity_update({ activityId, status, summary })
activity_complete({ activityId, summary })
activity_add_artifact({ activityId, artifactType, ... })
// Core tool discovery
tool_search({ query, enable: true })
// Step 1: Search
tool_search({ query: "jira" })
// Returns: jira_search_issues, jira_get_issue, jira_create_issue, ...
// Step 2: Call discovered tool
jira_search_issues({ jql: "project = PROJ AND status = Open" })
// Too broad - may not find what you need
tool_search({ query: "github" }) // Returns 20+ tools
// More specific - finds exactly what you need
tool_search({ query: "github content" }) // File content tools
tool_search({ query: "github repository" }) // Repo info tools
tool_search({ query: "github pull request" }) // PR tools
tool_search({ query: "create incident" })
tool_search({ query: "update widget" })
tool_search({ query: "query cmdb" })
tool_search({ query: "deploy business rule" })
tool_search({ query: "sys_script_include" })
tool_search({ query: "sp_widget" })
tool_search({ query: "sysevent_email_action" })
Tools follow consistent naming patterns:
| Pattern | Example | Purpose |
| --------------- | ------------------------ | --------------------- |
| snow_* | snow_query_table | ServiceNow operations |
| snow_deploy_* | snow_deploy_widget | Artifact creation |
| snow_update_* | snow_update_set_manage | Update operations |
| jira_* | jira_search_issues | Jira integration |
| azdo_* | azdo_search_work_items | Azure DevOps |
| confluence_* | confluence_create_page | Confluence |
| github_* | github_create_issue | GitHub |
| gitlab_* | gitlab_create_mr | GitLab |
Snow-Flow includes specialized MCP servers:
| Server | Purpose | Example Tools | | -------------------------- | --------------------- | -------------------- | | ServiceNow Unified | Core ServiceNow ops | Query, CRUD, scripts | | ServiceNow Development | Artifact management | Deploy, widget sync | | ServiceNow Automation | Script execution | Background scripts | | ServiceNow ITSM | IT Service Management | Incidents, changes | | ServiceNow Platform | Platform features | Flows, workspaces | | Enterprise | External integrations | Jira, Azure, GitHub |
tool_search firstenable: true is the default| Issue | Solution | | ----------------------- | ------------------------------- | | Tool not found | Try different query terms | | Too many results | Be more specific in query | | Tool doesn't work | Check parameters, may need auth | | Enterprise tool missing | Verify enterprise auth status |
// Discover
tool_search({ query: "incident" })
// Use discovered tools
snow_query_incidents({ filters: { active: true, priority: 1 } })
snow_create_incident({ short_description: "...", caller_id: "..." })
// Discover
tool_search({ query: "widget" })
// Use discovered tools
snow_find_artifact({ type: "widget", query: "incident" })
snow_widget_pull({ widget_name: "incident-dashboard", local_path: "./widgets" })
// Discover Jira tools
tool_search({ query: "jira" })
// Use discovered tools
jira_search_issues({ jql: "project = SNOW AND status = Open" })
jira_transition_issue({ issueKey: "SNOW-123", transition: "In Progress" })
development
This skill should be used when the user asks to "App Engine Studio", "workspace builder", "custom workspace", "AES", "low code", "app development", "studio", or any ServiceNow App Engine Studio development.
tools
This skill should be used when the user asks to "create a widget", "build a widget", "service portal widget", "sp_widget", "fix widget", "widget not working", "ng-click not working", or any Service Portal widget development.
development
This skill should be used when the user asks to "create chatbot", "virtual agent", "VA topic", "NLU", "conversation", "chat flow", "topic block", or any ServiceNow Virtual Agent development.
development
This skill should be used when the user asks to "vendor", "supplier", "contract", "procurement", "SLA", "vendor risk", "vendor performance", or any ServiceNow Vendor Management development.