Siya Dashboard Menu MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| GITHUB_REPO | No | GitHub repository name | app-insights-v2 |
| GITHUB_OWNER | No | GitHub repository owner | syia-ai |
| GITHUB_TOKEN | Yes | GitHub personal access token with repository permissions | |
| GITHUB_CONFIG_PATH | No | Path to the dashboard configuration file in the repository | dashboard-config.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dashboard_configA | Get the current complete dashboard configuration from GitHub |
| add_menu_sectionB | Add a new section to a client's dashboard menu |
| update_menu_sectionB | Update a specific section in a client's dashboard menu |
| remove_menu_sectionB | Remove a section from a client's dashboard menu |
| upload_dashboard_fileB | Upload an HTML dashboard file to S3 and add it as a menu section |
| list_eta_collectionsA | List all collections in the eta_raw_data_db MongoDB database |
| query_eta_dataB | Query data from a collection in the eta_raw_data_db MongoDB database (read-only) |
| count_eta_documentsA | Count documents in a collection with optional query filter |
| get_eta_distinct_valuesC | Get distinct values for a field in a collection |
| aggregate_eta_dataA | Execute MongoDB aggregation pipeline on eta data (read-only) |
| get_eta_collection_statsA | Get statistics about a collection (document count, size, indexes, etc.) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| section_management_guide | Comprehensive guide for managing dashboard menu sections |
| section_best_practices | Best practices for dashboard menu section management |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Dashboard Section Schema | JSON schema for dashboard menu section structure |
| Example Menu Section | Example of a dashboard menu section configuration |
TDQS
Scored across 11 tools
The tool set splits into two distinct domains—dashboard menu management and ETA data queries—with clear boundaries between them. However, upload_dashboard_file overlaps with add_menu_section because both add a menu section, and query_eta_data vs aggregate_eta_data could be confused by agents not deeply reading descriptions.
The dashboard tools follow an inconsistent verb_noun pattern (get_dashboard_config, add_menu_section, upload_dashboard_file), while the ETA tools consistently use verb_eta_noun. This cross-group inconsistency makes naming less predictable, though each group internally is fairly regular.
At 11 tools, the count is within a reasonable range, but the server packages two unrelated feature sets (dashboard menu editing and MongoDB data exploration) under one name. This makes the tool count feel over-scoped for the apparent core purpose of dashboard menu management.
The dashboard menu side covers CRUD plus file upload, and the ETA side covers common read-only query operations including count, distinct, aggregate, and stats. Missing menu reordering and direct menu section retrieval are minor gaps that agents can work around.