Databricks Field Guide by TechFabric

Follow a Databricks learning path

learn_path

Read-onlyIdempotent

Interactive: a curated learning path through the Field Guide, by role or goal (data-engineer-fundamentals, analytics-engineer, ml-engineer, platform-admin, snowflake-to-databricks, cost-control): its steps in order (a section to read, a concept to explore, a quiz), each with the call that opens it. Call it when the user asks "where do I start with Databricks", "a learning path for an analytics engineer" or "what should I learn next". Progress lives with the reader: send the steps done back as done. In a host that renders MCP Apps it opens as a map of the route with each step's story; the text is complete without it. No path: the list.

Input Schema

Name	Required	Description	Default
`done`	No	The steps the reader has done, by number or id (from an earlier result): progress lives with the reader, not the server
`path`	No	The path: data-engineer-fundamentals, analytics-engineer, ml-engineer, platform-admin, snowflake-to-databricks, cost-control. Omit it for the list.

Output Schema

Name	Required	Description
`for`	Yes
`next`	Yes
`path`	Yes
`asked`	Yes
`build`	Yes	The commit of the deploy that answered
`level`	Yes
`steps`	Yes
`title`	Yes
`ttlMs`	Yes	How long this answer may be kept before asking again, in milliseconds
`progress`	Yes
`withheld`	Yes
`available`	Yes
`index_built`	Yes	When this deploy's index was built (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026
- addedInput schema / properties / done / items / anyOf
```
Added value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  }
+]
```
- removedInput schema / properties / done / items / maxLength
```
Removed value: -200
```
- removedInput schema / properties / done / items / type
```
Removed value: -[
-  "string",
-  "integer"
-]
```
AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, the description discloses that progress is client-side ('progress lives with the reader: send the steps done back as done') and that MCP Apps hosts render a map while the text remains complete. These are meaningful behavioral details an agent would not get from annotations alone.

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?

The purpose is front-loaded, and the later sentences each carry distinct information about triggers, progress, rendering, and the no-path case. The opening sentence is dense with nested parentheticals, but overall the description is appropriately sized and has little waste.

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 read-only two-parameter tool with an output schema and full schema description coverage, the description covers purpose, trigger conditions, return structure, progress handling, and rendering fallback. An agent has everything needed to select and invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds useful semantics: the path values are enumerated and 'No path: the list' clarifies omission behavior. It also reinforces that 'done' comes from an earlier result and belongs to the reader rather than the server.

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: a curated learning path through the Field Guide, with named paths and a clear breakdown of the returned steps. It distinguishes itself from siblings like list_chapters and explore_concept by describing ordered steps that each include the call that opens them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit trigger phrases such as 'where do I start with Databricks' and 'a learning path for an analytics engineer', plus the 'what should I learn next' case. It does not name sibling alternatives like start_here or exam_prep to clarify when not to use this tool, so it falls just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Databricks Field Guide by TechFabric tools Inspect

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.