Skip to main content
Glama

list_dataset_releases

Semantic Scholar Datasets: list all available release ids (dated snapshots of the full corpus).

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": "list_dataset_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and adds only that releases are 'dated snapshots of the full corpus'. It says nothing about whether the call is a safe read, whether the listing is large or paginated, whether results are stable/immutable, or what the response looks like. For a zero-annotation tool this leaves the behavioral profile mostly undescribed.

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

Conciseness5/5

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

A single front-loaded sentence with a domain prefix, a specific verb, and no filler. Nothing is redundant or buried.

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

Completeness4/5

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

With no parameters and no output schema, the remaining burden is describing what comes back. 'Release ids' reasonably implies a list of identifiers, though the exact shape (plain ids vs. objects with dates) and ordering remain unspecified. Close to complete for a trivial enumeration 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly implies no inputs are needed to enumerate releases.

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 ('list all available release ids') and clarifies the domain concept with '(dated snapshots of the full corpus)', which distinguishes it from data-fetching siblings like get_dataset_release and get_dataset_diffs. It does not explicitly name those siblings, but the plural 'all available' plus the read-only listing framing makes its role distinguishable.

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?

Use is only implied: an agent can infer this is the discovery step before fetching a specific release or diffs, but the description never states when to use it, never names an alternative, and gives no prerequisites. Adequate but with a clear guidance gap.

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.