bc-telemetry-buddy-mcp 3.1.18 → 3.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +19 -0
- package/dist/cli.js +196 -117
- package/dist/server.js +181 -102
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [3.2.0] - 2026-03-04
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
- **MCP server-level instructions**: Added `instructions` field to the MCP `initialize` response — the standard MCP protocol mechanism for guiding any connected agent (GitHub Copilot, Claude Desktop, Cursor, etc.) on the correct tool-call workflow. Contains the mandatory 5-step sequence, forbidden patterns, multi-profile guidance, Application Insights table reference, and efficiency tips.
|
|
14
|
+
- **MCP workflow prompt**: Registered `bc-telemetry-workflow` prompt via `prompts/list` and `prompts/get` — a discoverable pull-based resource that agents can invoke to get concise workflow guidance.
|
|
15
|
+
- **Server instructions module** (`serverInstructions.ts`): New single-source-of-truth module exporting `SERVER_INSTRUCTIONS` and `WORKFLOW_PROMPT_CONTENT`, separated from tool definitions (SRP).
|
|
16
|
+
- **23 new tests**: Comprehensive test coverage for server instructions content, workflow prompt content, and `createSdkServer` integration (instructions in constructor, prompts capability, prompt registration, callback format).
|
|
17
|
+
|
|
18
|
+
### Changed
|
|
19
|
+
- **Softened `take 1 | project customDimensions` guidance**: Changed from "FORBIDDEN" to "UNNECESSARY" — `get_event_field_samples` already samples 20 rows internally with richer output (field types, occurrence rates, ready-to-use query), so the manual pattern is redundant rather than banned.
|
|
20
|
+
- **Strengthened `query_telemetry` tool description**: Now explicitly lists mandatory prerequisites in order and forbidden patterns directly in the tool description, ensuring agents see the guidance even without server instructions.
|
|
21
|
+
- **Added `prompts` capability**: MCP server now declares `prompts: { listChanged: true }` alongside existing `tools` and `logging` capabilities.
|
|
22
|
+
|
|
23
|
+
## [3.1.19] - 2026-03-04
|
|
24
|
+
|
|
25
|
+
### Changed
|
|
26
|
+
- **Value-driven discovery messaging across all response fields**: Updated `requiredNextStep` (catalog response), `schemaWarning` (query response), empty-KQL error message, and recommendations text to explain *why* calling `get_event_field_samples` is valuable (discover 20+ fields, learn exact types, see sample values, write correct KQL on first attempt) alongside the imperative enforcement.
|
|
27
|
+
- **Improved tool descriptions**: `get_event_catalog` now explicitly hints to call `get_event_field_samples` next with value reasoning. `get_event_field_samples` leads with "BEST PRACTICE: call this BEFORE writing KQL". `get_event_schema` nudges toward `get_event_field_samples` for full detail. `query_telemetry` emphasizes informing yourself about fields and types before forming KQL.
|
|
28
|
+
|
|
10
29
|
## [3.1.18] - 2026-03-03
|
|
11
30
|
|
|
12
31
|
### Changed
|