Skip to main content
Glama
manfye

Data.gov.my MCP Server

by manfye

list_catalogue_ids

Fetch available data catalogue IDs from Malaysia's government open data platform to discover and access datasets programmatically.

Instructions

Fetch list of available data catalogue IDs from GitHub repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'list_catalogue_ids' tool. Fetches list of JSON files from the GitHub repository 'data-gov-my/datagovmy-meta/contents/data-catalogue', extracts catalogue IDs, and returns them as JSON.
    if (name === 'list_catalogue_ids') {
      console.error('[GitHub] Fetching catalogue list from GitHub...');
      const response = await this.githubAxios.get('/repos/data-gov-my/datagovmy-meta/contents/data-catalogue');
      
      const catalogues = (response.data as GitHubFile[])
        .filter((item: GitHubFile) => item.type === 'file' && item.name.endsWith('.json'))
        .map((item: GitHubFile) => ({
          id: item.name.replace('.json', ''),
          name: item.name,
          download_url: item.download_url,
          size: item.size
        }));
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              catalogues,
              count: catalogues.length,
              message: 'Catalogue IDs fetched successfully from GitHub.'
            }, null, 2),
          },
        ],
      };
  • src/index.ts:77-81 (registration)
    Registration of the 'list_catalogue_ids' tool in the MCP server's tool list, including name, description, and empty input schema.
    {
      name: 'list_catalogue_ids',
      description: 'Fetch list of available data catalogue IDs from GitHub repository.',
      inputSchema: { type: 'object', properties: {}, required: [] },
    },
  • Input schema for 'list_catalogue_ids' tool: an empty object (no parameters required).
    inputSchema: { type: 'object', properties: {}, required: [] },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states 'Fetch list' which implies a read operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, returns paginated results, or what format the list comes in. The GitHub repository mention adds minimal context but insufficient for a mutation-free tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the key information ('Fetch list of available data catalogue IDs') with no wasted words. Every part of the sentence contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally adequate but lacks completeness. It specifies the source (GitHub repository) and what's fetched (IDs), but doesn't cover behavioral aspects like response format or error handling, leaving gaps for a read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any parameters. A baseline of 4 is justified since no parameters exist to explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Fetch list') and resource ('available data catalogue IDs from GitHub repository'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'search_catalogues' or 'get_catalogue_metadata', which might also retrieve catalogue-related information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'search_catalogues' or 'get_catalogue_metadata'. It mentions fetching from a GitHub repository, which gives some context, but lacks explicit when/when-not instructions or named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/manfye/data-dosm-mcp-nodejs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server