Commit b84418d
authored
Added server description to dab.draft.schema (#3405)
## Why make this change?
Closes #3282
The issue is that runtime MCP server description exists in code
(`McpRuntimeOptions.Description`) but was missing from the JSON schema,
so valid config using `runtime.mcp.description` could fail schema
validation. This change adds the missing schema entry, so config and
schema stay aligned.
## What is this change?
Added `runtime.mcp.description` to `schemas/dab.draft.schema.json` under
the `mcp` runtime properties:
- `type: "string"`
- description clarifying it is exposed as the MCP `instructions` field
in initialize response
No runtime/CLI code changes were needed because support already exists
in config model, converter, CLI configure option, and MCP server
response wiring.
## How was this tested?
- [ ] Integration Tests
- [x] Unit Tests
Ran:
- `dotnet test
src/Service.Tests/Azure.DataApiBuilder.Service.Tests.csproj --filter
"FullyQualifiedName~McpRuntimeOptionsSerializationTests" -v minimal`
## Sample Request(s)
CLI example:
```bash
dab configure --runtime.mcp.description "Use this MCP for product and inventory questions."
```
Config example:
```json
{
"runtime": {
"mcp": {
"enabled": true,
"path": "/mcp",
"description": "Use this MCP for product and inventory questions."
}
}
}
```1 parent fbe03e5 commit b84418d
1 file changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
280 | 280 | | |
281 | 281 | | |
282 | 282 | | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
283 | 287 | | |
284 | 288 | | |
285 | 289 | | |
| |||
0 commit comments