Skip to main content
Glama
musharna

data-aggregator-mcp

resolve

Fetch full metadata, file manifest, and optional citation for any research dataset using a DOI, Zenodo ID, or source-prefixed ID. Attaches identifiers and full-text when open access.

Instructions

Fetch the full DataResource for a known id (e.g. 'zenodo:7654321', 'datacite:10.5061/dryad.x', a bare Zenodo record id, or a DOI), including the complete files[] manifest. Publication resolve also attaches normalized identifiers (pmid/pmcid/doi) and, when open access, a full-text file. Pass cite= to render a citation onto the result (citation field); omitted means no citation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSource-prefixed id, bare Zenodo id, or DOI
citeNoOptional citation format to render onto the result: 'bibtex', 'ris', 'csl-json', or any CSL style name ('apa', 'mla', 'vancouver', ...). DOI-bearing records render via DOI content negotiation; non-DOI records support 'csl-json' only. Omitted = no citation. Failures degrade quietly (citation stays null).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
sourceYes
kindYes
titleYes
creatorsNo
yearNo
descriptionNo
doiNo
identifiersNo
accessionsNo
organismNo
taxaNo
subjectsNo
licenseNo
accessNo
filesNo
linksNo
citationNo
Behavior4/5

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

With no annotations, the description carries full burden. It discloses fetching full files manifest, attaching identifiers and full-text for publications, and citation rendering with graceful degradation. This is fairly transparent, though it could mention idempotency or side effects.

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?

The description is well-structured: front-loaded with main purpose, then details. Two sentences with no fluff, every sentence adds necessary information.

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?

Given 2 parameters and an output schema, the description provides complete context: what is returned (full DataResource, files, citation), optional cite behavior, and id examples. No gaps.

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%, baseline 3. The description adds value by giving id format examples and explaining cite parameter's supported formats, limitations (non-DOI records only support csl-json), and silent failure behavior, which goes beyond the schema.

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?

The description clearly states it fetches the full DataResource for a known id, including files manifest. It specifies additional behaviors for publications and optional citation rendering, distinguishing it from siblings like fetch, which likely provide a simpler view.

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

Usage Guidelines4/5

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

The description says 'for a known id', indicating when to use. It details the cite parameter's supported formats and failure handling, providing good usage context. However, it does not explicitly contrast with sibling tools or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musharna/data-aggregator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server