ARL-DMS 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 |
|---|---|
| dms_searchA | Search the ARL-DMS document library (14,535 indexed files across Drive root, Risk Team, Legal Data, Land, ESG sheets, SBU sheets, and BD Laws). Returns matching documents with name, path, drive id, url, doc type and source. |
| dms_listA | List documents in a DMS source repository (drive, risk-team, legal-data, land, sheet, bdlaws) with id, path, doc type and url. |
| dms_detailsA | Get a details card for one document by drive id or name: name, id, URL, path, doc type, source, and the 3-tier compliance mapping scaffold. |
| dms_fetchA | Fetch the text content of a publicly shared Google Drive document (docx/gdoc/xlsx/gslides/pdf attempts) by drive id. Returns up to 20k chars. |
| dms_risk_lookupA | Query the Bangladesh legal/compliance risk register (PostgreSQL, 8,288 risks) by keyword, category, or SBU. Returns risk code, title, scores, ratings, status. |
| dms_bdlaws_actA | Return the official Bangladesh law link and metadata for the 20 registered core business/corporate acts (Companies Act, Labour Act, VAT Act, etc.) from bdlaws.minlaw.gov.bd. |
| dms_statsA | Return DMS inventory statistics: total files/folders, counts by source and document type, registered sources, BD laws count. |
| dms_legal_registerA | Query the AKIJ Bangladesh Legal Universe (80 instruments) from the Legal Compliance Master Workbook: laws, domains, instrument type, regulator, official source URL. |
| dms_legal_requirementC | Query the Master Compliance Register (63 requirements, 119 fields) from the Legal Compliance Workbook: legal basis, obligation, applicability, owner, risk, evidence, compliance status. |
| dms_legal_riskB | Query the Compliance Risk Register (63 risks) from the Legal Compliance Workbook: risk statement, likelihood/impact, inherent/residual score, rating, owner, treatment. |
| dms_legal_controlsB | Query the Compliance Control Library (63 controls) from the Legal Compliance Workbook: control description, category, P/D/C, effectiveness, test method. |
| dms_legal_documentsB | Query the Documents & Records Register (63 records) from the Legal Compliance Workbook: required evidence, retention, storage, evidence class. |
| dms_legal_kpiA | Return compliance KPI/KRI definitions and Lookups (master data) from the Legal Compliance Workbook. |
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 13 tools
Each tool targets a distinct entity or action: document search vs. listing vs. details vs. fetch, plus separate registers for risks, controls, requirements, etc. The descriptions clearly differentiate them.
All tools use lowercase with underscores and the 'dms_' prefix. Some are verb-based (search, list, fetch) while others are noun-based (details, stats), showing minor inconsistency but overall predictable.
13 tools cover both document management and legal compliance without being overwhelming. Each tool serves a clear purpose, well-scoped for the server's domain.
The tool set covers searching, listing, retrieving documents, and querying multiple legal/compliance registers (risks, controls, requirements, documents). No obvious gaps for a read-only compliance DMS.