datasetsSearch the US DOT Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max datasets (1-100, default 20). | |
| query | No | Keyword to search dataset titles/descriptions (e.g. "budget", "crime", "health"). | |
| offset | No | Pagination offset. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "query": "traffic accidents"
+ },
+ {
+ "limit": 10,
+ "offset": 0,
+ "query": "highway safety"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations fully cover safety (readOnlyHint, idempotentHint, destructiveHint). Description adds value by specifying return fields (resource_id, name, description, category, update date) and linking to a subsequent tool.
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 sentences, no extra fluff. Clearly states purpose, return info, and usage hint. Ideal length.
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?
Given the tool's simplicity (3 optional params, rich annotations, no output schema), the description covers purpose, return values, and next steps. Fully adequate.
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 coverage is 100% and describes each parameter adequately. Description does not add additional meaning beyond what is already in the input schema for query, limit, offset.
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?
Description clearly states the tool searches the US DOT Open Data catalog by keyword and lists returned fields. The verb 'search' and specific resource distinguish it from unrelated sibling tools.
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?
Provides clear context for when to use this tool (searching DOT datasets) and hints at follow-up action ('pass the resource_id to query/metadata'). Does not explicitly exclude alternatives, but sibling tools are in different domains.
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.