You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An average MCP documentation server subsystem can't easily follow nested resources recursively, specifically if the content markup does not convey full URLs to be fetched subsequently. For example, the resource about CrateDB reference documentation's index page clearly demonstrates the situation.
There is a little innocent-looking backlog item, which is a leftover work item from the initial sweep of distilling a rough outline, where this obstacle has not been considered yet on a few spots.
- Outline: Revisit `notes` in `cratedb-outline.yaml`, for example about
pulling in `ctk docs functions` and `ctk docs settings`, but also about
other resources that have not been expanded properly yet
Details
The problem refers to the spots in cratedb-outline.yaml outlined below. It needs additional work in the spirit of curating ingredients optimally for this use case.
Tip
You can quickly discover is is not enough to enumerate high-level entrypoints of corresponding subsections of the knowledge tree when following corresponding link references: We need to dig deeper, in order to select, expand, and flatten relevant nested elements.
description: Examples, tutorials and runnable code on how to use CrateDB for time-series use cases. Exploratory data analysis, time-series decomposition, anomaly detection, forecasting.
notes: That's just the index again, and doesn't include any ingredients.
Problem
An average MCP documentation server subsystem can't easily follow nested resources recursively, specifically if the content markup does not convey full URLs to be fetched subsequently. For example, the resource about CrateDB reference documentation's index page clearly demonstrates the situation.
There is a little innocent-looking backlog item, which is a leftover work item from the initial sweep of distilling a rough outline, where this obstacle has not been considered yet on a few spots.
about/docs/backlog.md
Lines 7 to 9 in 7739eaf
Details
The problem refers to the spots in
cratedb-outline.yamloutlined below. It needs additional work in the spirit of curating ingredients optimally for this use case.Tip
You can quickly discover is is not enough to enumerate high-level entrypoints of corresponding subsections of the knowledge tree when following corresponding
linkreferences: We need to dig deeper, in order to select, expand, and flatten relevant nested elements.Enumerated spots
about/src/cratedb_about/outline/cratedb-outline.yaml
Lines 59 to 67 in 7739eaf
about/src/cratedb_about/outline/cratedb-outline.yaml
Lines 97 to 100 in 7739eaf
about/src/cratedb_about/outline/cratedb-outline.yaml
Lines 212 to 216 in 7739eaf
about/src/cratedb_about/outline/cratedb-outline.yaml
Lines 202 to 210 in 7739eaf