Skip to main content
Glama

get_dataset_release

Semantic Scholar Datasets: which datasets a release contains (papers, abstracts, citations, embeddings, s2orc, tldrs…). release_id defaults to 'latest'.

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

Input Schema

NameRequiredDescriptionDefault
release_idNolatest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden alone. It communicates that the tool reports dataset membership and that the identifier falls back to 'latest', but it says nothing about error behavior for an unknown release_id or whether the release list is stable. It is adequate for a simple read lookup but thin for a zero-annotation tool.

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 resource statement front-loaded and the default immediately after; the parenthetical example list efficiently conveys return content. The first sentence is a fragment rather than a clause, but nothing is wasted.

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 one-parameter, no-output-schema, no-annotation tool, the definition covers purpose and the default value, which is close to sufficient. The main missing piece is how to discover valid release_id values, which the description leaves entirely unaddressed.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry the single parameter, and it does state that release_id defaults to 'latest' — useful, though that same default is already declared in the schema. It does not explain what other valid values look like (date-stamped releases? version strings?) or how to obtain them, leaving the format underspecified.

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?

The description names the resource (a Semantic Scholar dataset release) and states precisely what is returned: which datasets the release contains, with concrete examples (papers, abstracts, citations, embeddings, s2orc, tldrs). An agent can tell this is a lookup of dataset composition rather than a listing of releases or download links, though it does not explicitly name the sibling tools that cover those related jobs.

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?

Usage is implied by the content statement rather than stated: an agent can infer this is the tool to call when it needs to know what is inside a given release. There is no explicit when-to-use framing and no routing to list_dataset_releases (to discover valid release IDs) or get_dataset_download_links (to actually fetch data), which are the obvious adjacent steps.

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.