Databricks Field Guide by TechFabric

Read a chapter

get_chapter

Read-onlyIdempotent

One chapter (or margin note) of the guide as clean Markdown with its code blocks intact, or one section of it: with its outline, its code blocks listed separately, its FAQs, when it last changed, and the official docs.databricks.com links it cites for the authoritative detail.

Input Schema

Name	Required	Description	Default
`slug`	Yes	A chapter's slug (lakebase, unity-catalog, start-here), a note's slug, or a guide URL or path. list_chapters has them; the field-guide-chapter prompt completes them.
`section`	No	One section only: its anchor (from search_guide, list_chapters or the outline) or its heading. Omit for the whole chapter.

Output Schema

Name	Required	Description
`url`	Yes
`code`	Yes
`docs`	Yes
`faqs`	Yes
`kind`	Yes
`next`	No	When this is about a concept the guide explains interactively: the call for a step-by-step walkthrough
`part`	Yes
`slug`	Yes
`build`	Yes	The commit of the deploy that answered
`title`	Yes
`ttlMs`	Yes	How long this answer may be kept before asking again, in milliseconds
`outline`	Yes
`section`	Yes
`summary`	Yes
`updated`	Yes	When the page last changed, YYYY-MM-DD
`markdown`	Yes	The chapter or section as Markdown, code blocks intact; links are absolute
`published`	Yes
`index_built`	Yes	When this deploy's index was built (ISO 8601)
`markdown_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedOutput schema / properties / next

Added value: +{
+  "description": "When this is about a concept the guide explains interactively: the call for a step-by-step walkthrough",
+  "properties": {
+    "arguments": {
+      "type": "object"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "arguments",
+    "hint"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / section / description

Previous value: -"One section only: its anchor (from search_guide or the outline) or its heading. Omit for the whole chapter."New value: +"One section only: its anchor (from search_guide, list_chapters or the outline) or its heading. Omit for the whole chapter."

changedInput schema / properties / slug / description

Previous value: -"A chapter's slug (lakebase, unity-catalog, start-here), a note's slug, or a guide URL or path"New value: +"A chapter's slug (lakebase, unity-catalog, start-here), a note's slug, or a guide URL or path. list_chapters has them; the field-guide-chapter prompt completes them."

First observedOct 19, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The description adds useful content-shape detail (code blocks, FAQs, last-changed, cited links) but says nothing about failure behavior when a slug or section is unknown, so it adds moderate rather than rich context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence stacked with parentheticals ('or margin note', 'or one section of it' followed by five parallel clauses), which makes the two modes harder to parse than they need to be. There is no wasted marketing language, but restructuring into an explicit whole-chapter vs section split would earn more.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't enumerate return values, and with rich annotations and fully documented parameters it covers both invocation modes adequately. The only genuine gap is guidance on what happens for an unknown slug or section.

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. The description goes beyond it by explaining the two operating modes: without a section you get the whole chapter as Markdown, with a section you get an outline, separately listed code blocks, FAQs and links, which genuinely sharpens how 'section' should be used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (a chapter, margin note, or a single section of the guide) and the output shape (clean Markdown, code blocks intact), so an agent can tell this is a read-a-chapter tool. It does not explicitly contrast itself with search_guide or list_chapters in the text, which keeps it short of 5.

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

Usage Guidelines3/5

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

Usage is only implied: you pass a slug or path and optionally a section to get content back. The description never states when to reach for this versus search_guide (discovery) or list_chapters (enumeration), and the only pointer to those siblings lives in the schema, not the description.

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.