Skip to main content
Glama

encode_log_derived_file

Log derived files from ENCODE data to create provenance records that link new files back to their original sources for tracking and reproducibility.

Instructions

Log a file you've derived from ENCODE data for provenance tracking.

Use this when you create new files from ENCODE data (e.g., running a pipeline, filtering peaks, merging samples). This creates a provenance record linking your derived file back to the original ENCODE source data.

WHEN TO USE: Use after creating files from ENCODE data (filtered peaks, merged signals). Creates provenance chain back to source. RELATED TOOLS: encode_get_provenance, encode_download_files

Args: file_path: Path to the derived file you created source_accessions: List of ENCODE accessions this file was derived from (experiment or file accessions, e.g., ["ENCSR133RZO", "ENCFF635JIA"]) description: What this derived file contains file_type: Type of file (e.g., "filtered_peaks", "merged_signal", "differential") tool_used: Tool/software used to create it (e.g., "bedtools intersect", "DESeq2") parameters: Parameters or command used

Returns: JSON with the provenance record ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
source_accessionsYes
descriptionNo
file_typeNo
tool_usedNo
parametersNo

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/ammawla/encode-toolkit'

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