NitroStack Calculator MCP Server
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculateC | Perform basic arithmetic calculations |
| convert_temperatureC | Convert temperature units based on file content or direct input. Supports Celsius (C) and Fahrenheit (F). |
| listConnectedAccountsA | Retrieve all connected Gmail accounts configured for the user. |
| fetchGmailNotificationsA | Fetch recent emails across all connected Gmail accounts. Returns a flattened list of notifications. |
| fetchSlackNotificationsA | Fetch recent Slack DMs, mentions, and channel messages. Returns a flattened list of notifications. |
| fetchJiraNotificationsA | Fetch recent Jira ticket updates (assignments, comments, and due dates). Returns a flattened list of notifications. |
| fetchCalendarEventsA | Fetch upcoming and recent calendar events. Returns a list of meetings in Notification format. |
| fetchGithubNotificationsA | Fetch recent GitHub notifications (PR review requests, CI failures, and mentions). Returns a flattened list of notifications. |
| buildUserContextA | Compile context about the user's current work state, including active project, upcoming meetings within the hour, and key collaborators. |
| prioritizeNotificationsA | Prioritize a list of notifications into Urgent, Normal, and FYI tiers based on the user's current work context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| calculator_help | Get help with calculator operations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Calculator Operations | List of available calculator operations |
| Health Checks | Current health status of all registered health checks |
| Calculator Result | UI component for Calculator Result |
| Priority Dashboard | UI component for Priority Dashboard |
| Widget Examples | Provides metadata and examples for all registered UI widgets |
TDQS
Scored across 10 tools
Each tool has a clear, distinct purpose: calculation, temperature conversion, fetching notifications from specific platforms (Slack, Jira, Calendar, GitHub, Gmail), building user context, prioritizing notifications, and listing Gmail accounts. There is no ambiguity between tools, as the platform or action is explicitly stated in the name/description.
Tool names follow mixed conventions: most use camelCase with a verb prefix (e.g., fetchSlackNotifications, buildUserContext), but one uses snake_case (convert_temperature) and another is a bare verb (calculate). Verbs also vary (calculate, fetch, build, prioritize, convert, list), so no consistent verb_noun pattern exists.
At 10 tools, the count is within the typical 3-15 range and not excessive. However, the server's stated 'Calculator' purpose is served by only two tools (calculate, convert_temperature), while the majority focus on notification aggregation, so the count feels somewhat misaligned with the server name but is still reasonable for the actual feature set.
The notification aggregation workflow is fairly complete: fetching from five platforms, building user context, and prioritizing. However, the calculator functionality is minimal (basic arithmetic and temperature only), missing many expected operations like unit conversions or scientific functions. Additionally, there is no 'mark as read' or 'send' action for notifications, so the domain has notable gaps.