SLA.directory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLA_API_BASE | No | Base URL for the SLA.directory API | https://sla.directory/api/v1 |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vendorsA | Search SLA.directory for vendors and services by name or category (e.g. 'datadog', 'storage', 'payments'). Returns slugs to look up. |
| get_vendorA | Get a vendor's SLA (uptime, credit policy, claim process, per-service SLAs). Accepts a slug or a vendor name (fuzzy). Returns a cited summary by default; pass format:'raw' for the full record. |
| get_service_slaA | Get per-service SLAs for a vendor (many platforms publish a separate SLA per service). Optionally filter to one service by name. |
| compare_vendorsA | Compare key SLA terms across several vendors (uptime, max credit, claim window, automatic credits, service count), each with its source. |
| list_categoriesA | List all SLA.directory categories with vendor counts. |
| vendors_in_categoryA | List vendor summaries in a category (use list_categories for the slug, e.g. 'finance-and-payments'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| sla_review | Summarize one vendor's SLA: uptime, credits, claim process, exclusions, weakest services. |
| compare_for_renewal | Compare several vendors' SLA terms for a contract renewal decision. |
| weakest_services | Find a vendor's lowest-uptime services to plan error budgets. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: comparing vendors, fetching per-service SLAs, retrieving vendor details, listing categories, searching, and listing vendors by category. There is no overlap in functionality.
Most tools use a verb_noun pattern (compare_vendors, get_service_sla, get_vendor, list_categories, search_vendors). However, 'vendors_in_category' uses a noun_preposition_noun structure, breaking the pattern slightly.
With 6 tools, the set is well-scoped for an SLA directory. It covers essential operations without being too numerous or too few, providing a focused interface.
The tools cover searching, browsing by category, retrieving vendor details, per-service SLAs, and cross-vendor comparison. This represents a comprehensive read-only surface for the domain, with no obvious gaps.