ARL-CMS 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 |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cms_list_requirementsA | List/filter compliance requirements from the CMS catalog (584 requirements / 80 domains / 11 categories). Filters: query, domain, category, owner, applicability. Returns up to 200 rows. |
| cms_get_requirementA | Get full 13-field detail of a single compliance requirement by name (what it is, why, how it should work, minimum requirements, evidence, pass criteria, non-compliance triggers, owner). |
| cms_check_complianceA | 3-tier compliance resolver: (1) internal policy/SOP library, (2) Bangladesh law (risk register + bdlaws), (3) global standard (584-requirement catalog). Reports coverage gaps explicitly. Tier 2 (Bangladesh law) is the mandatory floor. |
| cms_search_policyA | Search the internal ARL policy/SOP/manual library (Tier 1) for a topic. Hybrid integration: resolves real documents from the shared ARL-DMS index (14,535 entries) first, falls back to live Drive. Returns matched documents with name, path, drive id, url, source. For document text/OCR use ARL-DMS MCP dms_fetch. |
| cms_risk_lookupB | Look up Bangladesh legal risks from the risk register (2,612 rows) by SBU, area, or topic, with specific legal basis, possible liability/penalty, and risk level. |
| cms_bdlaws_actA | Return the official Bangladesh law link and metadata for the 20 registered core business/corporate acts from bdlaws.minlaw.gov.bd (Tier 2 mandatory statutory floor). |
| cms_document_complianceB | Compliance mapping for ERP document types (55 types) in 3-tier order - T1 internal policy/SOP/manual, T2 Bangladesh law, T3 global standard, plus indicative owner. |
| cms_business_documentsB | Inventory of ERP business documents (42 types) with schema/table and ERP process mapping; filter by module, process, tax. |
| cms_coverage_scanB | Library-to-standard coverage scan: maps the 584-requirement catalog domains/categories and reports counts and registered assets. |
| cms_gap_reportC | Coverage gap report: requirements whose domain has no candidate internal document match, plus Bangladesh risk-register summary. |
| cms_statsA | Return CMS inventory statistics: total requirements, domains, categories, risk register rows, document types, business documents, BD laws. |
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 11 tools
Most tools have distinct purposes (listing requirements, getting detail, checking compliance, searching policy, etc.). However, cms_list_requirements and cms_coverage_scan both deal with the 584-requirement catalog and domains, which could cause some confusion—cms_coverage_scan specifically reports domain/category counts and assets, but the distinction may not be immediately clear to an agent.
All tools follow a consistent and informative prefix pattern: cms_ followed by a verb_underscore_noun (e.g., cms_list_requirements, cms_check_compliance, cms_get_requirement). This makes it easy to predict tool behavior from the name alone.
With 11 tools, the server is well-scoped. Each tool addresses a specific compliance-related task or query, and the number feels appropriate for the domain—neither too sparse nor overwhelming. The tool count supports effective navigation without redundancy.
The tool surface covers the main compliance workflow: listing/fetching requirements, checking compliance against multiple tiers, searching internal policies, looking up risks, and mapping documents. Minor gaps exist—for example, there is no tool to add or update requirements or internal policies, and no direct way to fetch full document content (but that is handled by another MCP server).