Skip to main content
Glama

Data Gov Sg Search Datasets

data_gov_sg_search_datasets
Read-onlyIdempotent

Search the data.gov.sg dataset catalog by keyword (e.g. "rainfall", "hawker centres", "resale flat prices"), real text search via data.gov.sg's own site search, since the official v2 catalog API has none. Returns matching COLLECTIONS (topics that may bundle several datasets, e.g. one per year) with each dataset's real dataset_id for get_dataset / query_dataset. Omit query to browse the raw catalog unfiltered instead, paged 10/page (~4,600 datasets total).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "rainfall"
    },
    "name": "data_gov_sg_search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page (10 results per page either way)
queryNoKeyword search, e.g. "rainfall", "COE prices", "population". Omit to browse unfiltered.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered; the description adds genuinely new behavior: search is implemented via data.gov.sg site search because the v2 catalog API has none, results are collections rather than datasets, and the corpus is ~4,600 datasets paged 10/page. It does not discuss relevance/ranking quality or limits on search behavior, which keeps it from the top of the scale given the annotations already carry the safety story.

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

Conciseness4/5

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

Front-loaded with the core verb and scope, and every clause carries information (mechanism, result granularity, browse mode, corpus size). It is a single dense paragraph with stacked parentheticals, which makes it slightly heavier to parse than necessary.

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

Completeness4/5

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

For a two-parameter, fully documented search tool with an output schema, this covers what an agent needs: input modes, result granularity, pagination, and sibling routing. Minor gaps remain around search relevance behavior and ordering of results, but nothing essential to correct invocation is missing.

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

Parameters3/5

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

Schema coverage is 100% and both parameters already document the same details (keyword examples, 10 results per page, omit to browse). The description largely restates that rather than adding syntax or formatting nuance, so the baseline 3 applies; the only marginal addition is the clarification that a query matches collections rather than individual datasets.

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

Purpose5/5

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

States a specific verb+resource ("Search the data.gov.sg dataset catalog by keyword") and immediately distinguishes this tool from data_gov_sg_get_dataset and data_gov_sg_query_dataset, which it says consume the returned dataset_id. It also discloses a non-obvious result granularity (matching COLLECTIONS, not individual datasets), so an agent knows exactly what kind of answer to expect.

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

Usage Guidelines5/5

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

Explicitly covers both modes: supply a keyword for text search, or "Omit `query` to browse the raw catalog unfiltered instead". It also routes follow-up work to the sibling tools by naming the returned dataset_id as the input for get_dataset / query_dataset, so the when-and-what-next is fully specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.