Skip to main content
Glama

get_dataset_diffs

Semantic Scholar Datasets: incremental diff (added/updated/deleted) for a dataset between two releases. Needs the key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset_name": "<dataset_name>",
      "start_release": "<start_release>"
    },
    "name": "get_dataset_diffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_releaseNolatest
dataset_nameYes
start_releaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the useful behavioral fact that results are categorized as added/updated/deleted and that an API key is required, but it says nothing about pagination, rate limits, or how large diffs are returned.

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?

Two short sentences with the core purpose front-loaded and the auth requirement appended. Nothing is wasted, though the second sentence is terse to the point of being cryptic ('the key').

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read tool with no output schema, the description covers purpose and result categories adequately. It falls short on what release strings look like, where dataset names come from, and the shape of the returned diff, which an agent must guess.

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

Parameters2/5

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

Schema description coverage is 0% across 3 parameters. 'Between two releases' hints at start_release/end_release, but dataset_name format, valid release identifiers, and the fact that end_release defaults to 'latest' are all left to the schema titles alone.

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

Purpose4/5

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

States a specific verb and resource: an incremental diff (added/updated/deleted) for a dataset between two releases. That is clearly distinct from get_dataset_release or list_dataset_releases, though the description never explicitly names or contrasts those siblings.

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

Usage Guidelines3/5

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

The phrase 'between two releases' implies the use case (comparing releases), and 'Needs the key' flags an auth prerequisite. There is no explicit when-to-use vs. alternatives guidance and no statement of when a diff is inappropriate versus fetching a full release.

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.