Find datasets added, changed, or removed since a specified date, plus portal-reported updates, with an optional portal filter.
Datasets added, changed or removed in the index since a date, and datasets whose portal says they were updated since then. Optional portal filter.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| since | Yes | YYYY-MM-DD | |
| portal | No | source_id or part of a portal name |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses the dual inclusion logic (index changes vs portal-reported updates) but omits limit/pagination behavior, ordering, return shape, and any permission/rate-limit context.
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, front-loaded with the selection criteria, and no unnecessary wording. The optional filter note is efficient.
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?
For a 3-parameter query tool with no annotations and no output schema, the description covers the core selection logic but omits the limit parameter and return/pagination details. It is adequate but not complete.
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 67%. The description clarifies 'since' as a date and 'portal' as an optional filter, but never mentions the 'limit' parameter, which has no schema description. It adds partial meaning but leaves one parameter undocumented.
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 names the resource (datasets) and the temporal scope (added, changed, removed since a date; portal-reported updates), so the purpose is clear. It does not explicitly distinguish itself from search_datasets or other siblings, so it falls short of a 5.
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?
It implies usage for finding recent index or portal changes and notes an optional portal filter, but gives no explicit when-to-use vs alternatives (e.g., search_datasets) or when-not conditions. Guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.