Skip to main content
Glama

Dataset licence facts

by uk.datalicense
OverviewDiscussionsAdmin

dataset_licence

Retrieve licence facts for one Hugging Face dataset: declared licence, where it was declared, recorded source datasets, detected licence files and a signal. Each licence value comes with an evidence URL linking to the Hub file, API record, file list or Hub page that was checked, with a commit-specific link where available. For datasets in the daily build, facts come from the build by default. Other public datasets are checked live on the Hugging Face Hub. Signal values: permissive = permissive or share-alike licence reported; restrictive = use restrictions reported; conflict = possible licence conflict; unclear = insufficient or unrecognised licence information. These signals do not establish permission to use a dataset. Licence facts reported by the dataset and its declared sources. Not legal advice, and not a grant of permission to use the dataset.

Input Schema

NameRequiredDescriptionDefault
idYesDataset ID, for example 'owner/name'.
liveNoCheck the Hub now instead of using the facts published by the daily build. Datasets not in the build are always checked live.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / live / description
      Previous value: -"Check the Hub now instead of using the weekly index. Datasets outside the index are always checked live."New value: +"Check the Hub now instead of using the facts published by the daily build. Datasets not in the build are always checked live."
  2. Changed1 schema field changed
    • addedInput schema / properties / live
      Added value: +{
+  "description": "Check the Hub now instead of using the weekly index. Datasets outside the index are always checked live.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does a lot: it explains the two data paths (daily build vs live Hub check), that each value carries an evidence URL with commit-specific links, exactly what each signal value means, and it explicitly warns that signals do not establish permission. It omits failure behavior for private/nonexistent datasets and any rate-limit or latency implications of live checks.

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 verb and returned fields, and the signal glossary is genuinely useful. Some redundancy: 'These signals do not establish permission to use a dataset' and the closing 'Not legal advice, and not a grant of permission' say the same thing twice, and 'Licence facts reported by the dataset and its declared sources' restates the opening.

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 output schema, the description does the work of enumerating return values, evidence URL semantics, and signal meanings, which is what an agent needs. The remaining gap is edge-case behavior for datasets that cannot be checked (private, gated, or nonexistent), which matters because the live path can fail.

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 description coverage is 100%, so both parameters are already documented, including the live flag's semantics. The description's statement that build data is used by default for build datasets adds slight nuance about the default, but largely restates the schema, so the baseline of 3 applies.

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 verb and resource ('Retrieve licence facts for one Hugging Face dataset') and enumerates the exact payload: declared licence, declaration location, source datasets, licence files, signal, plus evidence URLs. An agent can distinguish this from the only sibling, find_datasets, which is a search tool, without opening either schema.

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?

Useful build-vs-live guidance ('For datasets in the daily build, facts come from the build by default. Other public datasets are checked live on the Hub') tells the agent when the default path applies. However, there is no explicit statement of when to use this tool versus find_datasets, and no prerequisites for the required id (e.g. private/gated datasets).

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

All Dataset licence facts toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources