datapulse-my

Overview Schema Source Related Servers Score Discussions Admin

Find Malaysian Public Data

search_datasets

Read-onlyIdempotent

Find Malaysian public datasets by topic, source, or licence. Get ranked matches with metadata to discover relevant data before verifying reliability.

Instructions

Use for discovery only: find DataPulse's 418 Malaysian public datasets by topic, source, or licence—for example, 'Malaysian public data inflation', licence and attribution, or a government dataset source. Returns ranked matches with id, title, source, licence, published status, and score. This is not trust verification: a status is published pipeline context, not proof that a dataset is current or reliable. For 'is this dataset current?' or verify before relying on data, use search_datasets → verify_dataset → get_provenance.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum discovery matches to return; integer from 1 to 50, e.g. 10.
`query`	Yes	Topic or task phrasing for Malaysian public-data discovery only, e.g. 'Malaysian public data inflation'; verify a result separately.
`source`	No	Optional case-insensitive publisher/source filter, e.g. 'OpenDOSM'.
`licence`	No	Optional exact licence name or supported alias for reuse discovery, e.g. 'CC BY 4.0'; this does not verify attribution compliance.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.12.0Sep 9, 2026

changedInput schema / properties / licence / description

Previous value: -"Optional exact licence name or supported alias, e.g. 'CC BY 4.0'."New value: +"Optional exact licence name or supported alias for reuse discovery, e.g. 'CC BY 4.0'; this does not verify attribution compliance."

changedInput schema / properties / limit / description

Previous value: -"Maximum ranked matches to return; integer from 1 to 50, e.g. 10."New value: +"Maximum discovery matches to return; integer from 1 to 50, e.g. 10."

changedInput schema / properties / query / description

Previous value: -"Free-text search terms; natural language is allowed, e.g. 'inflation cpi'."New value: +"Topic or task phrasing for Malaysian public-data discovery only, e.g. 'Malaysian public data inflation'; verify a result separately."

changedInput schema / properties / query / examples

Previous value: -[
-  "inflation cpi"
-]New value: +[
+  "Malaysian public data inflation"
+]

changedInput schema / properties / source / description

Previous value: -"Optional case-insensitive source-name substring, e.g. 'OpenDOSM'."New value: +"Optional case-insensitive publisher/source filter, e.g. 'OpenDOSM'."

Addedv1.0.2Sep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent safety, so the bar for added behavioral value is met by the description's caveat that 'a status is published pipeline context, not proof that a dataset is current or reliable.' It also discloses return fields and ranking, which is useful beyond the schema.

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?

The description is 3 sentences and front-loads the key 'discovery only' purpose. The exampls in the first sentence are slightly extraneous but useful for grounding the query phrasing; overall no sentence is wasted.

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

Completeness5/5

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

For a 4-parameter tool with a rich schema and output schema, the description fully equips an agent: purpose, caveats, return content, and a reroute for verification. It even provides a compond tool chain, leaving no practical gap for correct invocation.

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%, so the baseline is 3. The description recaps that query/source/licence are the search dimensions and gives examples, but does not add meaning beyond the detailed schema descriptions already present for each parameter.

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?

The description uses a specific verb ('find') and a precise resource ('DataPulse's 418 Malaysian public datasets') with explicit search dimensions: topic, source, or licence. It clearly separates discovery from trust verification, distinguishing itself from sibling tools like verify_dataset and get_provenance without needing to open their schemas.

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?

It explicitly says 'Use for discovery only' and states what the tool is not: 'This is not trust verification.' It gives a concrete routing rule for currentness/reliability checks: 'search_datasets → verify_dataset → get_provenance.' This is strong when-to-use versus when-not-to-use guidance.

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