Agent Paywire library

Get one dataset card

get_dataset

Read-onlyIdempotent

Return one training or eval dataset card by id: name, publisher, url, access (open, login, or terms-acceptance), mirror_allowed and notes. A card is metadata only; this does not download dataset files, so follow url for the data. Take the id from list_datasets entries, or from changes_since after removing the dataset: prefix. An unknown id returns an isError result (the card file is 404). Use list_datasets to browse or compare cards, and search_library with category datasets-benchmarks for papers about datasets. Free, no auth.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Dataset id exactly as in list_datasets entries[].id, e.g. agentpaywire-library. Do not include the dataset: prefix that changes_since uses.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`name`	Yes
`notes`	Yes
`access`	Yes
`publisher`	Yes
`mirror_allowed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / id / description

Previous value: -"Dataset id. Example: agentpaywire-library."New value: +"Dataset id exactly as in list_datasets entries[].id, e.g. agentpaywire-library. Do not include the dataset: prefix that changes_since uses."

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / id / description

Previous value: -"Dataset id, for example agentpaywire-library or elliptic."New value: +"Dataset id. Example: agentpaywire-library."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "access": {
+      "enum": [
+        "open",
+        "login",
+        "terms-acceptance"
+      ],
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "mirror_allowed": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "type": "string"
+    },
+    "publisher": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "publisher",
+    "url",
+    "access",
+    "mirror_allowed",
+    "notes"
+  ],
+  "type": "object"
+}

AddedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, but the description adds value beyond them: metadata-only (no file download), unknown id yields an isError/404, and no auth is required. These are behavioral facts an agent cannot infer from the annotations alone.

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 purpose and scope, then constraints and alternatives; every sentence carries information. It is dense and runs several sentences, but none are filler or restatements of the name.

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

Completeness5/5

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

An output schema exists so return structure needn't be explained, yet the description still names the returned fields and the error path. With one required parameter and full annotation coverage, nothing needed to invoke this correctly is missing.

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?

Schema coverage is 100% and the schema already documents the id parameter, including the 'dataset:' prefix caveat. The description adds the id's provenance (list_datasets entries[].id or changes_since with prefix removed), which is genuine added meaning beyond the schema's format note.

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 ('Return one training or eval dataset card by id') and enumerates the card's fields. It also immediately clarifies scope ('metadata only; this does not download dataset files'), which distinguishes it from any data-fetching sibling.

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

Usage Guidelines5/5

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

Explicitly routes the agent: take the id from list_datasets entries or from changes_since after stripping the 'dataset:' prefix, and names list_datasets for browsing/comparison and search_library for dataset-related papers. This is exactly the when-to-use-this-vs-alternatives guidance the dimension asks for.

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

All Agent Paywire library tools Inspect

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

Need Help?