Discover available tools and resources in Databricks workspace. Use when: (1) User asks 'what tools are available', (2) Before writing agent code, (3) Looking for MCP servers, Genie spaces, UC functions, or vector search indexes, (4) User says 'discover', 'find resources', or 'what can I connect to'.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Run tool discovery BEFORE writing agent code to understand what resources are available in the workspace.
uv run discover-toolsOptions:
# Limit to specific catalog/schema
uv run discover-tools --catalog my_catalog --schema my_schema
# Output as JSON
uv run discover-tools --format json --output tools.json
# Save markdown report
uv run discover-tools --output tools.md
# Use specific Databricks profile
uv run discover-tools --profile DEFAULT| Resource Type | Description | MCP URL Pattern |
|---|---|---|
| UC Functions | SQL UDFs as agent tools | {host}/api/2.0/mcp/functions/{catalog}/{schema} |
| UC Tables | Structured data for querying | (via UC functions) |
| Vector Search Indexes | RAG applications | {host}/api/2.0/mcp/vector-search/{catalog}/{schema} |
| Genie Spaces | Natural language data interface | {host}/api/2.0/mcp/genie/{space_id} |
| Custom MCP Servers | Apps starting with mcp-* | {app_url}/mcp |
| External MCP Servers | Via UC connections | {host}/api/2.0/mcp/external/{connection_name} |
After discovering tools:
databricks.yml - See add-tools skill for YAML snippetsuv run start-app - See run-locally skillNeed a resource that doesn't exist yet? See the create-tools skill.
b5b790d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.