Preview a Saudi open dataset by providing its registry dataset_id to inspect its structure and sample data.
Fetch and preview a dataset for an exact registry dataset_id.
| Name | Required | Description | Default |
|---|---|---|---|
| dataset_id | Yes | Exact canonical dataset_id from the registry. Examples: 'sama-pos-weekly', 'stats-gov-sa-cpi-headline-monthly'. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. 'Fetch and preview' implies a read operation, but the description does not clarify whether preview returns a sample, full data, or any limits, nor does it mention side effects or permissions. This is thin for a tool that previews data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The entire description is one clean, front-loaded sentence: 'Fetch and preview a dataset for an exact registry dataset_id.' Every word earns its place, with no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one parameter) and has an output schema, which reduces the need to explain return values. However, the description lacks behavioral context (e.g., what 'preview' entails) and usage guidance relative to siblings, leaving an agent to infer when this is the right choice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with a well-documented dataset_id parameter including examples. The description's reiteration of 'exact registry dataset_id' reinforces but does not add meaning beyond the schema. Baseline of 3 is appropriate for complete schema coverage with no additional parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Fetch and preview') and resource ('dataset') with a clear qualifier ('exact registry dataset_id'). This is unambiguous about what the tool does, though it does not explicitly name or contrast against siblings like download_dataset or query_dataset, relying on the name 'preview' to differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use guidance is provided. The description only mentions the prerequisite of an exact registry dataset_id, which implies you need it, but there is no mention of alternatives (e.g., search_datasets for finding IDs, download_dataset for full data) or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.