aminghadersohi opened a new pull request, #40299:
URL: https://github.com/apache/superset/pull/40299

   ### SUMMARY
   
   Adds `list_reports` and `get_report_info` MCP tools for the Alerts & Reports 
domain, following the canonical database domain pattern.
   
   **New files:**
   - `superset/mcp_service/report/schemas.py` — `ReportFilter`, `ReportInfo`, 
`ReportList`, `ListReportsRequest`, `GetReportInfoRequest`, `ReportError`, 
`serialize_report_object()`
   - `superset/mcp_service/report/tool/list_reports.py` — lists alerts/reports 
with filtering, search, pagination
   - `superset/mcp_service/report/tool/get_report_info.py` — fetches a single 
schedule by numeric ID
   
   **Key design decisions:**
   - `ReportFilter` restricts filterable columns to: `name`, `type`, `active`, 
`dashboard_id`, `chart_id`
   - `GetReportInfoRequest.identifier` is `int` only (`ReportSchedule` has no 
UUID or slug)
   - `owners` field is defined in `ReportInfo` but stripped by 
`filter_user_directory_fields` (same privacy pattern as other list tools)
   - No `data_model_metadata` privacy gate (reports are user-level content, not 
database metadata)
   - Tools registered in `app.py` and advertised in `DEFAULT_INSTRUCTIONS`
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   N/A — backend-only MCP tools
   
   ### TESTING INSTRUCTIONS
   
   ```bash
   # Run unit tests for the new domain
   pytest tests/unit_tests/mcp_service/report/ -v
   
   # Verify tools register and are callable via MCP client
   # list_reports: call with empty request → returns paginated report list
   # get_report_info: call with {"identifier": <id>} → returns schedule metadata
   ```
   
   ### ADDITIONAL INFORMATION
   
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration
   - [x] Introduces new feature or API
   - [ ] Removes existing feature or API


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to