Skip to main content
Glama

Data Gov Sg Get Dataset

data_gov_sg_get_dataset
Read-onlyIdempotent

Dataset metadata + column schema.

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_get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_idYesDataset ID (e.g. "d_8b84c4ee58e3cfc0ece0d773c8ca6abc")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is fully covered. The description adds only the return payload ('metadata + column schema'), which is largely redundant given the output schema; it says nothing about behavior on an unknown or malformed dataset_id or about rate limits.

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 words plus a conjunction — nothing wasted and the payload is front-loaded. It is terse to the point of being a fragment rather than a sentence, but no wording needs cutting.

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?

For a single-parameter read tool with an output schema and full annotations, most of the burden is carried elsewhere. The missing piece is workflow context: whether a valid dataset_id comes from search_datasets and that this tool typically precedes query_dataset.

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 the single dataset_id parameter is documented in the schema with a concrete example. The description adds no meaning beyond that, so the baseline 3 applies.

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

Purpose3/5

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

The fragment "Dataset metadata + column schema" names the resource and the payload, so an agent can infer it retrieves a dataset's metadata and column schema. But there is no verb and no explicit differentiation from siblings such as data_gov_sg_query_dataset or data_gov_sg_search_datasets — the agent must infer that this is the lookup rather than the query or search path.

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?

No when-to-use guidance at all: nothing says this is the step before data_gov_sg_query_dataset, or that search_datasets is how you find the dataset_id in the first place. The only clue is the example ID in the schema.

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.