Skip to main content
Glama

Data Gov Sg Query Dataset

data_gov_sg_query_dataset
Read-onlyIdempotent

Fetch rows from a dataset. Supports limit, offset, and filter map (column -> value).

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": {
      "dataset_id": "d_8b84c4ee58e3cfc0ece0d773c8ca6abc"
    },
    "name": "data_gov_sg_query_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-10000 (default 100)
offsetNo0-based row offset
filtersNoColumn-value filter map
dataset_idYesDataset ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds no behavior beyond that: no statement about pagination ceiling enforcement, whether the filter map is exact-match or supports operators, or whether unbounded offsets error out. "Supports limit, offset, and filter map" restates the schema rather than explaining behavior.

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?

Two short sentences, the core action front-loaded with the control surface immediately after. No filler. It is arguably too terse for the tool's complexity, but nothing is redundant.

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?

The tool has an output schema, so return-value description is not required, and annotations cover safety. What is missing is workflow context: where a dataset_id comes from and how paging should be driven across a large result set. For a 4-parameter dataset reader that is a real but moderate gap.

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 description coverage is 100% and each parameter carries its own description (range 1-10000 with default 100, 0-based offset, column-value filter map, dataset ID), plus examples in the schema. The description's one added nuance is writing the filter direction as "column -> value", which matches the schema but adds no new semantics such as value typing or multi-filter AND/OR behavior.

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 names a concrete verb and resource ("Fetch rows from a dataset") and enumerates the shifting/filtering controls, so the agent can tell this is a row-retrieval tool rather than a metadata tool. It does not explicitly contrast itself with data_gov_sg_get_dataset or data_gov_sg_search_datasets, leaving that separation to inference from sibling names.

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?

There is no when-to-use guidance at all: nothing says this is the call to make after locating a dataset_id, nor when to prefer get_dataset (metadata) or search_datasets (discovery). The agent must infer the workflow ordering from the required dataset_id parameter alone.

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.