feat(teams): add variables and MCP tool filter#25
Conversation
|
The latest Buf updates on your PR. Results from workflow buf-pr / buf (pull_request).
|
Test & Lint SummaryCommands:
Tests: passed 2, failed 0, skipped 0. |
Ready for reviewAdds two features to the Teams proto and OpenAPI schemas: 1. Variables entity
2. MCP tool filter config
CI: buf lint ✅, buf build ✅, spectral validate ✅ |
noa-lucent
left a comment
There was a problem hiding this comment.
The Variable entity and MCP tool filter additions are well-structured and follow the proto and OpenAPI patterns cleanly overall. The CRUD RPCs, path definitions, and pagination schemas are all consistent.
One major issue: Variable.yaml uses a nested meta property instead of the allOf composition pattern used by every other entity schema. This would produce a different JSON shape for consumers and must be aligned.
Two minor items on toolFilter required fields and resolve response semantics — see inline comments.
Summary
Test & Lint SummaryCommands:
Tests: passed 2, failed 0, skipped 0. |
noa-lucent
left a comment
There was a problem hiding this comment.
All three prior comments verified as resolved in code:
- Variable.yaml — now uses
allOfcomposition withEntityMeta.yaml, consistent with all other entity schemas. ✅ - McpServerConfig.yaml —
required: [mode]added totoolFilter. ✅ - variable-resolve.yaml —
valueremoved fromrequired, description added. ✅
Proto definitions, OpenAPI schemas, and path specs are clean and consistent. LGTM.
Summary
Testing
Related #24