Skip to main content
Glama

Mdexa

What changed in a list of datasets

check_changes

What changed in the cards of a list of datasets or models since a date: license status, conditions, risk flags, verification date, change log. No account: slugs (up to 50) and since (YYYY-MM-DD). With an API key: save_as stores the list (subscribe=true sends notifications); later send only watchlist_id. Registered entries come back as unverified_registered. Use before repeating an earlier conclusion; not for searching. One call counts once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
hintsNo
sinceNoYYYY-MM-DD; not needed with watchlist_id.
slugsNo
modelsNoStored with the list, not tracked yet.
save_asNoName to store the slugs as (API key).
subscribeNo
watchlist_idNoSaved list id (API key); no slugs with it.

Output Schema

NameRequiredDescriptionDefault
changedNo
summaryNo
unchangedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real context the annotations don't carry: the anonymous path, that save_as persists a list, that subscribe=true sends notifications, and that registered entries surface as unverified_registered. 'One call counts once' signals a quota/cost model but never says what it counts against, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome, then structured into anonymous-mode and API-key-mode clauses, with the usage rule last. The telegraphic fragments ('No account: ...', 'With an API key: ...') are dense but readable; a couple of phrases like 'One call counts once' trade clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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 described, and the description covers the remaining complexity: auth tiers, persistence side effects, quota, and the watchlist reuse loop. The only omission is the meaning of lang and hints, which is minor for an 8-parameter optional-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description compensates for the important parameters: it explains since's format, save_as's storage behavior, subscribe's effect, and the mutual exclusivity of watchlist_id vs slugs. It leaves lang, hints, and models unexplained, and its 'slugs (up to 50)' guidance conflicts with the schema's maxItems of 500, which could mislead an agent on batch size.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific operation (detect what changed in cards of a list of datasets or models since a date) and enumerates the changed fields: license status, conditions, risk flags, verification date, change log. It explicitly separates itself from search tools with 'not for searching', so an agent can distinguish it from search_datasets without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger ('Use before repeating an earlier conclusion') and an explicit exclusion ('not for searching'), plus the two operating modes (no account vs API key) and the follow-up pattern of reusing watchlist_id. It stops short of naming a specific sibling to use instead of this one for lookups, so the routing guidance is clear but not fully closed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.