MCP Server for Apache OpenDAL™
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listB | |
| readB | |
| get_infoB | |
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 3 tools
Each tool has a clearly distinct purpose: get_info retrieves metadata, list lists directory contents, and read reads file content. There is no overlap between them.
Tools follow a verb_noun pattern (get_info, list, read), but 'list' and 'read' lack a noun component, which is a minor inconsistency. Overall, the naming is predictable.
With only 3 tools, the server covers only read operations, which is too few for a full-featured storage abstraction like OpenDAL. Many essential operations (create, delete, update) are missing.
The tool surface is severely incomplete for the stated purpose. It only provides read and listing capabilities, leaving out write, delete, and other management operations required for a storage server.