Data.gov.my 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_catalogue_idsB | Fetch list of available data catalogue IDs from GitHub repository. |
| get_catalogue_metadataB | Fetch metadata for a specific data catalogue by ID from GitHub. |
| get_catalogue_dataC | Fetch actual data from the data.gov.my API for a specific catalogue. |
| search_cataloguesC | Search for catalogues by keyword in their names or descriptions. |
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 4 tools
Each tool has a clearly distinct purpose: list_catalogue_ids enumerates available IDs, get_catalogue_metadata retrieves metadata for a specific ID, get_catalogue_data fetches actual data for a catalogue, and search_catalogues performs keyword searches. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_catalogue_data, list_catalogue_ids). The verbs (get, list, search) are appropriately chosen and consistently applied, making the naming predictable and readable.
With 4 tools, this server is well-scoped for its purpose of interacting with data catalogues. Each tool serves a distinct and necessary function, and the count is neither too sparse nor excessive, fitting typical expectations for a focused API client.
The toolset covers core operations for browsing and retrieving catalogue information (list, search, get metadata, get data), providing a solid foundation. A minor gap exists in lacking update or management operations, but this is reasonable for a read-only data access server, and agents can work effectively with the available tools.