Skip to main content
Glama

get_dataset_download_links

Semantic Scholar Datasets: get download links (presigned URLs) for one dataset in a release. Needs the API 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>"
    },
    "name": "get_dataset_download_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_idNolatest
dataset_nameYes

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 two behavioral facts beyond the schema: the output is presigned URLs (implying time-limited, credential-scoped links) and an API key is required. It does not say whether the links expire, how long they remain valid, or whether the call is read-only.

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, front-loaded with the namespace and verb, with the auth requirement placed last. Nearly every word earns its place, though the 'Semantic Scholar Datasets:' prefix and 'Needs the API key' are terser than ideal prose.

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 two-parameter tool with no output schema and no annotations, the definition covers purpose and auth but leaves return shape, link expiry, and parameter formats unaddressed. It is adequate to attempt a call but not complete enough to predict results.

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%, so the description must compensate for both parameters. It only gestures at them via 'one dataset in a release'; it gives no format or allowed values for dataset_name and never mentions release_id or the 'latest' default, leaving both parameters under-specified.

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 gives a specific verb ('get download links') and resource ('download links for one dataset in a release') and clarifies the return is presigned URLs. That is enough to distinguish it from sibling dataset tools such as get_dataset_release or get_dataset_diffs, though it doesn't name an alternative explicitly.

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 only implied by 'for one dataset in a release'. The one real guideline is the prerequisite 'Needs the API key', which is useful, but there is no statement of when to choose this over get_dataset_release or get_dataset_diffs, and no exclusions.

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.