msc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_notification_categoriesA | Lấy danh sách loại thông báo từ hệ thống Mua sắm công |
| get_notificationsC | Lấy danh sách thông báo theo loại từ hệ thống Mua sắm công |
| get_notification_detailA | Lấy chi tiết một thông báo theo ID từ hệ thống Mua sắm công |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: listing notifications, listing categories, and fetching a single notification by ID. There is no ambiguity between them despite all being 'get' operations.
All tool names follow the same `get_notification_*` pattern with consistent snake_case and verb-first naming. This makes the set predictable and easy to navigate.
Three tools is a lean but appropriate set for a read-only notification retrieval service. It covers the essential operations without unnecessary bloat, though it is on the smaller end of the ideal range.
The tools provide the core lifecycle for viewing notifications: list all, filter by category, get categories, and fetch details. There is no update or delete, but this appears to be a read-only public procurement notification system, so the coverage is adequate with only minor potential gaps like search or pagination.