StatusCraft
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Check the live status of a specific service (e.g. 'github', 'openai', 'stripe'). Returns operational/degraded/partial_outage/major_outage/maintenance. |
| get_all_statusA | Check the live status of ALL tracked services at once. Returns a summary grouped by status — useful for a quick health check across the stack. |
| list_servicesA | List services tracked by StatusCraft, with their IDs and tags. Use this to discover service IDs for get_status. Supports name/ID search and tag filtering. Results are paginated (100 per page) — pass page to get more. |
| check_multipleA | Check the live status of a specific list of services in parallel. Faster than calling get_status repeatedly. |
| refresh_statusA | Force a fresh live fetch for one or all services, bypassing the 60-second cache. Use this when you need the absolute latest status — e.g. during an active incident or immediately after a known outage ends. |
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 5 tools
Tools are mostly distinct. get_status, get_all_status, and check_multiple all retrieve statuses but with different scopes (single, all, custom list). Descriptions clarify the differences, though an agent might still confuse get_all_status and check_multiple.
Naming follows verb_noun pattern generally, but verbs are inconsistent (check, get, list, refresh). 'check_multiple' uses an adjective instead of a noun, breaking the pattern. Overall readable but not fully consistent.
5 tools is well-scoped for a service status checking server. Each tool serves a clear purpose without excess, covering listing, single/get-all/custom status checks, and cache refresh.
Covers core needs: discover services, fetch status (individual, all, custom list), and force refresh. Minor gaps like historical statuses or adding/removing services are absent but not critical for the stated purpose.