describe_datasetRead a dataset’s freshness, coverage, provenance URLs, limitations, and explicit public/account/paid access status.
| Name | Required | Description | Default |
|---|---|---|---|
| dataset_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| dataset | Yes |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesRemoved value: -falseOutput schema / properties / dataset / properties / current_release / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "as_of": {
- "type": "string"
- },
- "attribution_url": {
- "format": "uri",
- "type": "string"
- },
- "data_dictionary_url": {
- "format": "uri",
- "type": "string"
- },
- "documentation_url": {
- "format": "uri",
- "type": "string"
- },
- "download_url": {
- "format": "uri",
- "type": "string"
- },
- "formats": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "manifest_url": {
- "format": "uri",
- "type": "string"
- },
- "map_url": {
- "format": "uri",
- "type": "string"
- },
- "published_at": {
- "format": "date-time",
- "type": "string"
- },
- "spatial_coverage": {
- "type": "string"
- },
- "temporal_coverage": {
- "type": "string"
- },
- "version": {
- "type": "string"
- }
- },
- "required": [
- "version",
- "published_at",
- "as_of",
- "spatial_coverage",
- "temporal_coverage",
- "formats",
- "manifest_url",
- "documentation_url",
- "attribution_url",
- "data_dictionary_url",
- "download_url",
- "map_url"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "as_of": {
+ "type": "string"
+ },
+ "attribution_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "data_dictionary_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "documentation_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "download_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "formats": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "manifest_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "map_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "published_at": {
+ "format": "date-time",
+ "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+ "type": "string"
+ },
+ "spatial_coverage": {
+ "type": "string"
+ },
+ "temporal_coverage": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "version",
+ "published_at",
+ "as_of",
+ "spatial_coverage",
+ "temporal_coverage",
+ "formats",
+ "manifest_url",
+ "documentation_url",
+ "attribution_url",
+ "data_dictionary_url",
+ "download_url",
+ "map_url"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context by naming the metadata categories returned, including explicit access-tier disclosure, but says nothing about failure behavior when a dataset is unknown or the caller lacks account/paid entitlement.
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?
One dense sentence with the resource and the informative payload front-loaded and no filler. The list of attributes borders on enumerating return fields that the output schema already covers, but it is compact enough to earn its place.
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?
An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a tool whose only input is an opaque id and whose nearest sibling has a near-identical name, the description leaves both id sourcing and sibling differentiation unaddressed.
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 0% and the single required parameter dataset_id is never mentioned in the description. It gives no hint about the identifier format, where such ids come from (presumably search_datasets), or whether slugs are accepted, so it fails to compensate for the coverage gap.
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 gives a specific verb ("read") and resource (a dataset's metadata) and enumerates exactly which attributes are surfaced: freshness, coverage, provenance URLs, limitations, and access status. It does not distinguish itself from the similarly named sibling describe_dynamik, leaving ambiguity about which tool returns what.
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?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as describe_dynamik or search_datasets. The agent must infer that this is a metadata lookup rather than a sampling or search operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.