search_datasetsSearch public-safe Dynamik dataset metadata. Results declare release availability and do not imply account entitlement.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
| Name | Required | Description | Default |
|---|---|---|---|
| datasets | Yes |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesRemoved value: -falseOutput schema / properties / datasets / items / 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 cover the safety profile exhaustively (readOnly, idempotent, non-destructive, closed-world), lowering the bar. The description does add genuinely useful context beyond them: that results only declare release availability and confer no entitlement. But it omits search behavior such as matching rules, result limits, or what an empty query returns.
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?
Two short sentences, no filler, with the scope constraint front-loaded. Nothing is redundant with the title or schema.
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-value documentation is not required, and the entitlement caveat is a valuable addition. Still, for a search tool with an undocumented free-text parameter and no alternatives guidance, key calling details remain 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 `query` parameter has no description in the schema. The description never mentions the parameter at all — no syntax, no matching semantics, no note about matching fields (name vs. metadata). With low coverage the description was required to compensate and does not.
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?
States a specific verb (search) and resource (Dynamik dataset metadata) with a meaningful scope qualifier ('public-safe'). It does not, however, distinguish itself from siblings like describe_dataset or get_dataset_sample_link, so an agent must infer the boundary.
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?
The description says nothing about when to use this tool versus describe_dataset, describe_dynamik, or get_dataset_sample_link. The second sentence is a caveat about interpreting results, not guidance on selecting or invoking the tool.
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.